When to use
Indefinite symbolic integration. The constant of integration is omitted.
Input schema
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
}
},
"required": [
"expression",
"variable"
],
"additionalProperties": false
}Response shape
All tools return { ok: true, result } on success and { ok: false, error } on failure. The result object contains:
| Field | Type | Description |
|---|---|---|
| result | string | Resulting expression in nerdamer syntax. |
Example
Request
{
"expression": "x * sin(x)",
"variable": "x"
}Response
{
"ok": true,
"result": {
"result": "-cos(x)*x+sin(x)"
}
}curl
curl -X POST https://tools.aieo.se/api/v1/integrate \
-H 'Content-Type: application/json' \
-d '{"expression":"x * sin(x)","variable":"x"}'MCP call (JSON-RPC)
MCP clients call this tool as tools/call against /api/mcp:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "integrate",
"arguments": {
"expression": "x * sin(x)",
"variable": "x"
}
}
}Common errors
- Integrand has no elementary antiderivative.Nerdamer returns an unevaluated `integrate(…)` placeholder.
{ "expression": "exp(-x^2)", "variable": "x" } - 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`.