Skip to main content
Glama
The-40-Thieves

codecalc

by The-40-Thieves
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Symbolic

symbolic
Read-onlyIdempotent

Run symbolic math operations: solve equations, solve linear systems, simplify expressions, or compute limits. Choose the operation and provide the expression to get exact algebraic results.

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. 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
NameRequiredDescriptionDefault
opYesWhich symbolic operation to run: 'solve', 'solve_linear', 'simplify', or 'limit' (each has its own required params)
varNoVariable to solve for or take the limit over; optional, default 'x'; used by op='solve'/'limit'
exprNoExpression or equation to solve/simplify/take the limit of; required by op='solve'/'simplify'/'limit'
pointNoPoint `var` approaches for op='limit'; optional, default 'oo' (infinity)
systemNo';'-separated equations for op='solve_linear', e.g. 'x + y = 10; x - y = 2'; required by that op
variablesNoComma-separated variable names for op='solve_linear', e.g. 'x, y'; required by that op

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.12.0
    • 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"
  2. Addedv0.11.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly=true, destructive=false, and idempotent=true, so the safety profile is covered. The description adds meaningful behavioral detail beyond that: each op returns the same result as the retired standalone tool plus an additive op field, solve accepts equations/expressions, and limit has a default 'oo'. It stops short of documenting error cases (e.g., no real roots, malformed expression, unsupported syntax), so it is not a 5.

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

Conciseness3/5

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

The description is information-dense and its per-op parallel structure makes it scannable, but it is long and partially restates what the schema already says for each parameter. For a 6-parameter tool this length is mostly justified; it earns a middle score rather than a higher one because some sentences repeat schema content rather than adding new guidance.

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

Completeness4/5

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

For a complex op-dispatch tool, the description covers operation selection, parameter requirements per op, input formats, worked examples, and migration from the former tools. Remaining gaps are minor: no mention of multiple solutions, no solution, or parse-error behavior. Together with the 100% schema coverage and output schema, this is nearly complete.

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%, providing a baseline of 3; the description adds real value on top: concrete equation strings ('2*x + 1 = 0'), the exact system syntax for solve_linear ('x + y = 10; x - y = 2'), which params each op requires vs. treats as optional, and the default variable/point behavior. This reduces ambiguity beyond what the schema alone offers.

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 opens by identifying the tool as a symbolic-math dispatcher with four named operations (solve, simplify, factor, limit), each paired with a concrete verb and resource. It also situates itself against the retired standalone tools and names sibling tools like z3_check, so an agent can immediately tell what the tool does and how it differs from alternatives.

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?

The description gives per-op selection guidance: use solve for equations, simplify/factor for expressions, limit for limits, and explicitly redirects non-symbolic numeric work to calc_exact and constraint solving to z3_check. It also names the four former standalone tools that this dispatch tool replaces, making the migration path and op-selection criteria unambiguous.

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

Deploy Server

Other Tools