Limit

One-sided/limit-at-a-point evaluation. Use `infinity` for ∞.

Validated server-side with Zod. The same schema feeds OpenAPI and the MCP tool list.

{
  "type": "object",
  "properties": {
    "expression": {
      "type": "string",
      "minLength": 1
    },
    "variable": {
      "type": "string",
      "minLength": 1
    },
    "value": {
      "type": "string",
      "minLength": 1,
      "description": "Limit point, e.g. '0', 'pi', 'infinity'"
    }
  },
  "required": [
    "expression",
    "variable",
    "value"
  ],
  "additionalProperties": false
}

All tools return { ok: true, result } on success and { ok: false, error } on failure. The result object contains:

Request

{
  "expression": "sin(x)/x",
  "variable": "x",
  "value": "0"
}

Response

{
  "ok": true,
  "result": {
    "result": "1"
  }
}

curl -X POST https://tools.aieo.se/api/v1/limit \
  -H 'Content-Type: application/json' \
  -d '{"expression":"sin(x)/x","variable":"x","value":"0"}'

MCP clients call this tool as tools/call against /api/mcp:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "limit",
    "arguments": {
      "expression": "sin(x)/x",
      "variable": "x",
      "value": "0"
    }
  }
}

• Two-sided limit does not exist.
  Result may be `NaN`, `undefined`, or a one-sided value without warning.
• A required field is missing or has the wrong type.
  Zod validation error, e.g. `Required` or `Expected string, received number`.
• Nerdamer cannot parse the expression (unbalanced parens, unknown function, stray characters).
  `Unexpected token …` or `… is not a valid expression`.