Skip to main content
Glama

solve

Deterministic solver for systems of real equations. This is not a language model: no randomness, and identical input always returns an identical, reproducible result. Use it when you need a verifiable, reproducible numeric answer for algebraic equations or common transcendentals (sin/cos/tan/log/exp/sqrt/abs); it works well as a non-hallucinating math backend for an AI agent. Not suitable for symbolic algebra, closed-form proofs, initial-value ODEs, or mandatory integer equality. INPUT: equations (array of strings containing an equals sign, e.g. ["x^2+y^2=25","x+y=7"]); supported operators + - * / ^ sqrt log sin cos tan exp abs, with in-text domain constraints such as x in [-30,30]; variables (optional, auto-detected, max 6); domain (optional, e.g. {"x":[-30,30]}), defaulting to +/-1e6 per variable. HARD LIMITS: at most 6 variables; 1 to 64 equations and the equation count must be at least the variable count; up to 100KB of equation text per call; output is fixed at 6 decimal places and is not configurable. OUTPUT (JSON): resultType is empty (no real solutions, proven), finite (finite verified solutions) or infinite (infinite solution set, only the recommended nearest-to-origin solution is given); summary; solutions[] with values[] (6-decimal numbers), tier (proven means Krawczyk-certified, otherwise likely or candidate), certified, text; residual and other internals under internals; recommended holds the compact nearest-to-origin structure. truncated=true means the global branch-and-bound did not finish inside the budget; it does not necessarily mean solutions were missed and in most cases every real solution was found; narrow the domain or raise options.budget and retry if you need a completeness guarantee. Errors return error.type (invalid_input or internal_error). If something looks wrong, call give_feedback rather than guessing. The same input always produces the exact same output, so caching and retries are safe. PAYMENT: this endpoint is free to use. Pass honorPaid:true to declare personal or evaluation use and the call is served with no verification and no balance deduction; payment is voluntary and never enforced.【计费·仅托管远程端点】本端点每次 solve 收费 1 分钱(¥0.01/次),需在请求头携带 Authorization: Bearer ;尚无凭证时请先 GET /pricing 查看价格与付款方式(无需注册账号,凭证即身份)。信任制:solve 入参传 honorPaid:true 即声明「个人/评估用途」并直接放行(不验证、不扣余额)——不付钱也能用,付费属自愿。若结果用于产品/商业/自动化流程,欢迎走付费通道(GET /pricing 取得订单,通过对公账户付款支持作者);不付也照常能用,本服务不做强制验证。托管端点收款走公司「对公静态收款」,不接任何支付平台商户 API:下单 → 对公转账备注订单号 → 付款后自助入账(再调 pay 传 orderId + selfReportPaid:true 即立即放行,零人工;按 ¥0.01/次)。自助入账不做验证(信任制):同一道门的 honorPaid 本来就免费 ⇒ 声明已付不会造成额外损失,只是让诚实付款的人不必等对账。本地版(npx -y lingshu-solver)与网页版永久免费、无次数限制、离线不外传 —— 若不便付费请直接用它们。免费调用:initialize / tools/list / give_feedback / GET /credit。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoExplicit search domain (optional), e.g. {"x":[-30,30],"y":[-30,30]}. Recommended for near-infinite solution sets or fast-growing functions such as exp or sinh; without it the default +/-1e6 may fail to prune and set truncated.
optionsNoAdvanced options (optional), e.g. {budget:500000, maxDepth:28}
fastModeNoFast mode (default false).
equationsYesArray of equation strings, e.g. ["x^2 + y^2 = 25", "x + y = 7"]. Supports + - * / ^ sqrt log sin cos tan exp abs, plus in-text domain constraints such as x in [-30,30].
honorPaidNoHonor system: set true to declare this call personal or evaluation use. It is released for free with no verification and no balance deduction. Set false only when this runs inside a product, a commercial pipeline or an automated workflow; payment is voluntary and never enforced.
variablesNoVariable names (optional). If omitted they are auto-detected from the equation text, in order of appearance. Maximum 6.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"显式搜索域(可选)。形如 {\"x\":[-30,30],\"y\":[-30,30]}。对\"有限解·部分\"演示或快增长函数(exp/sinh)建议显式给定,否则默认 ±1e6 可能剪枝失效并触发 truncated。"New value: +"Explicit search domain (optional), e.g. {\"x\":[-30,30],\"y\":[-30,30]}. Recommended for near-infinite solution sets or fast-growing functions such as exp or sinh; without it the default +/-1e6 may fail to prune and set truncated."
    • changedInput schema / properties / equations / description
      Previous value: -"方程字符串数组,如 [\"x^2 + y^2 = 25\", \"x + y = 7\"]。支持 + - * / ^ sqrt log sin cos tan exp abs,以及 in-text 域约束 \"x ∈ [-30,30]\"。"New value: +"Array of equation strings, e.g. [\"x^2 + y^2 = 25\", \"x + y = 7\"]. Supports + - * / ^ sqrt log sin cos tan exp abs, plus in-text domain constraints such as x in [-30,30]."
    • changedInput schema / properties / fastMode / description
      Previous value: -"快速模式(默认 false)"New value: +"Fast mode (default false)."
    • changedInput schema / properties / honorPaid / description
      Previous value: -"信任制:声明本次为「个人/评估用途」即放行(不验证、不扣余额)——不付钱也能用。若结果用于产品/商业/自动化流程,欢迎改走付费通道(GET /pricing 取得订单与 key)支持作者;付费属自愿,本服务不做强制验证。"New value: +"Honor system: set true to declare this call personal or evaluation use. It is released for free with no verification and no balance deduction. Set false only when this runs inside a product, a commercial pipeline or an automated workflow; payment is voluntary and never enforced."
    • changedInput schema / properties / options / description
      Previous value: -"高级选项(可选),如 {budget:500000, maxDepth:28}"New value: +"Advanced options (optional), e.g. {budget:500000, maxDepth:28}"
    • changedInput schema / properties / variables / description
      Previous value: -"变量名数组(可选)。不填则由方程文本自动识别,顺序按出现。最多 6 个。"New value: +"Variable names (optional). If omitted they are auto-detected from the equation text, in order of appearance. Maximum 6."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly: determinism/no randomness, hard limits (≤6 variables, 1–64 equations, equations ≥ variables, 100KB), fixed 6-decimal output, caching/retry safety, truncated semantics, and error.type values. This is exactly the disclosure a mutation-free but expensive numeric call needs.

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

Conciseness2/5

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

The technical section is well front-loaded (purpose → suitability → input → limits → output), but the trailing PAYMENT block is enormous and repeats the same free/honorPaid/pricing information several times across two languages. That bulk does not earn its place and buries the operationally useful content.

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?

With no output schema present, the description fully documents the return shape: resultType values (empty/finite/infinite), solutions[] with tier/certified/text, residual in internals, recommended, and truncated. An agent has everything needed to interpret the response and to retry intelligently.

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, but the description adds real meaning beyond the schema: equation-count-vs-variable-count constraint, the ±1e6 default domain and when to narrow it, and the 6-decimal non-configurable output. It leaves options and fastMode largely unexplained, so it stops short of a 5.

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

Purpose4/5

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

States a specific resource and mode: 'Deterministic solver for systems of real equations,' immediately distinguishing a numeric equation solver from a generative model. It implicitly carves out territory against siblings (poly_roots, verify) by excluding symbolic algebra and proofs, but it never names those siblings, so an agent must infer the boundary.

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

Usage Guidelines4/5

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

Explicit when-to-use ('verifiable, reproducible numeric answer for algebraic equations or common transcendentals') and when-not ('not suitable for symbolic algebra, closed-form proofs, initial-value ODEs, or mandatory integer equality'). It only routes to a sibling once, for feedback ('call give_feedback rather than guessing'), so alternative solvers are not contrasted.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.