codecalc

by The-40-Thieves

Overview Schema Source Related Servers Discussions Admin

Python

Local

Symbolic

symbolic

Read-onlyIdempotent

Solve equations and systems, simplify expressions, and compute limits using symbolic algebra.

Instructions

Symbolic algebra, selected by op — replaces the four former standalone tools solve_expression, solve_linear, simplify_expression and limit_expression, retired in 0.12.0 (CHANGELOG.md). Every op returns exactly its former tool's own result, plus op (additive).

op="solve" (was solve_expression) — the roots of one equation: 'x**2 - 4 = 0', '2*x + 1 = 7'. For a system of several equations, use op="solve_linear". For general constraint satisfiability (inequalities, boolean constraints, multiple solvers), use z3_check. Returns solutions as a list of strings alongside the parsed equation and variable. Used by this op: expr (required), var (optional).

op="solve_linear" (was solve_linear) — a system of equations sharing variables; despite the name, non-linear systems work too (e.g. 'x2 + y2 = 5; x - y = -1'). Example: system='x + y = 10; x - y = 2', variables='x, y'. Used by this op: system, variables (both required).

op="simplify" (was simplify_expression) — simplify, factor, and expand an expression — algebraic forms, not solving (use op="solve") and not a numeric value (use calc_exact). Returns simplified, factored, and expanded as strings alongside the parsed original. Used by this op: expr (required).

op="limit" (was limit_expression) — asymptotic behaviour: limit of expr as var -> point. 'symbolic("limit", "n*log(n)/n**2", "n")' returns 0 — settles complexity arguments faster than arguing. Used by this op: expr (required), var (optional), point (optional).

Input Schema

TableJSON Schema

Name	Required	Description
`op`	Yes	Which symbolic operation to run: 'solve', 'solve_linear', 'simplify', or 'limit' (each has its own required params)
`var`	No	Variable to solve for or take the limit over; optional, default 'x'; used by op='solve'/'limit'
`expr`	No	Expression or equation to solve/simplify/take the limit of; required by op='solve'/'simplify'/'limit'
`point`	No	Point `var` approaches for op='limit'; optional, default 'oo' (infinity)
`system`	No	';'-separated equations for op='solve_linear' (non-linear systems work too, e.g. 'x2 + y2 = 5; x - y = -1'), e.g. 'x + y = 10; x - y = 2'; required by that op
`variables`	No	Comma-separated variable names for op='solve_linear', e.g. 'x, y'; required by that op

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.13.0Sep 23, 2026

changedInput schema / properties / system / description

Previous value: -"';'-separated equations for op='solve_linear', e.g. 'x + y = 10; x - y = 2'; required by that op"New value: +"';'-separated equations for op='solve_linear' (non-linear systems work too, e.g. 'x**2 + y**2 = 5; x - y = -1'), e.g. 'x + y = 10; x - y = 2'; required by that op"

Changed6 schema fields changedv0.12.0Sep 9, 2026

addedInput schema / properties / expr / description

Added value: +"Expression or equation to solve/simplify/take the limit of; required by op='solve'/'simplify'/'limit'"

addedInput schema / properties / op / description

Added value: +"Which symbolic operation to run: 'solve', 'solve_linear', 'simplify', or 'limit' (each has its own required params)"

addedInput schema / properties / point / description

Added value: +"Point `var` approaches for op='limit'; optional, default 'oo' (infinity)"

addedInput schema / properties / system / description

Added value: +"';'-separated equations for op='solve_linear', e.g. 'x + y = 10; x - y = 2'; required by that op"

addedInput schema / properties / var / description

Added value: +"Variable to solve for or take the limit over; optional, default 'x'; used by op='solve'/'limit'"

addedInput schema / properties / variables / description

Added value: +"Comma-separated variable names for op='solve_linear', e.g. 'x, y'; required by that op"

Addedv0.11.0Sep 9, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context: it explicitly states that every op returns the former tool's result plus an additive `op` field, and it documents return shapes like `solutions`, `simplified`, `factored`, and `expanded`. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, but the length is justified by the four-operation dispatch structure and is organized into clear op-labeled sections. It is front-loaded with the purpose and replacement note. Minor editorial asides like 'settles complexity arguments faster than arguing' could be trimmed, but they do not undermine clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete for a multi-operation tool: it specifies all op values, their required and optional parameters, gives examples for each mode, and routes between alternatives. Since an output schema exists, the explicit return-field descriptions are a bonus rather than a necessity. No critical gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by grouping parameters per operation, stating which are required for each op, and providing illustrative examples such as system='x + y = 10; x - y = 2' and variables='x, y'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly defines the tool as a symbolic algebra dispatcher selected by `op`, and enumerates the four operations with concrete examples. It distinguishes this tool from its former standalone counterparts and from nearby tools like z3_check and calc_exact.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage guidance is explicit and action-oriented: use op='solve_linear' for systems, op='solve' for single equations, op='simplify' for algebraic forms rather than solving, and z3_check for constraint satisfiability. It also names calc_exact as the alternative for numeric evaluation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.