Skip to main content
Glama

solve

Read-only

Solves linear equations and systems exactly with no/infinite solution reports, finds all real roots of one nonlinear equation in a range, and numerically solves square nonlinear systems in calc syntax.

Instructions

Solve equations in calc syntax: linear equations/systems exactly (reports no/infinite solutions), one nonlinear equation (all real roots in range), square nonlinear systems numerically.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "solve"
  }
}

Input Schema

NameRequiredDescriptionDefault
guessNostart point {x:1}
rangeNo[min,max] for one unknown
equationNoe.g. "3x+2=11"; no "=" means =0
equationsNosystem
variablesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true; the description goes beyond that by disclosing exact-vs-numeric solving, that no/infinite solutions are reported, and that nonlinear roots are bounded by a range. Still missing: what a non-square system does, whether solutions return symbolic or decimal forms, and any convergence/failure behavior for the numeric path.

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?

A single dense sentence with no filler, and the equation-class distinction is front-loaded. The heavy abbreviation of the three modes makes it slightly harder to parse than a short bulleted structure would be, but nothing is wasted.

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

Completeness3/5

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

With no output schema, the description must carry more of the return-value story, and it only says that no/infinite solutions are reported. With zero required parameters and five optional ones (equation, equations, variables, range, guess), the description does not make clear which combinations are valid for each mode, which is the main completeness gap.

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

Parameters3/5

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

Schema coverage is 80%, so parameter meanings are largely documented in the schema. The description only marginally helps by tying 'range' to the one-unknown case and implying the choice between 'equation' and 'equations', but it never explains 'guess' or 'variables' beyond what the schema already says.

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 verb (solve) and the three distinct equation classes it handles: exact linear equations/systems, one nonlinear equation over a range, and square nonlinear systems numerically. An agent can tell it is a math solver rather than an evaluator like calc, though the boundary with 'calc' is only implied through 'calc syntax'.

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

Usage Guidelines3/5

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

Supported cases are enumerated, which implicitly signals when the tool applies, but there is no explicit when-to-use versus the sibling 'calc' or any statement of what happens with unsupported inputs (e.g., non-square systems). Usage must be inferred from the mode list.

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