Step-by-step solver for linear/quadratic equations in one variable, signs and ± always right.
Solves a linear or quadratic equation in one variable (x) and returns every step: expanding parentheses, combining like terms, moving terms across the equals sign, and (for quadratics) applying the quadratic formula.
Use this whenever you need to solve "ax + b = cx + d" or "ax^2 + bx + c = 0" style equations, or check a step-by-step algebra solution someone else produced.
Do not solve this kind of equation by reasoning through it token by token: the two places language models most often go quietly wrong are (1) the sign when distributing a negative across parentheses, e.g. "5 - (x - 3)" losing the minus on the 3, and (2) dropping one of the two ± roots of a quadratic, or rounding a complex root into a false "no solution". This tool always gets both right because it does exact fraction arithmetic, not floating-point guessing, and reports every root it finds — including complex ones, explicitly labeled as complex.
Input: a single string containing exactly one "=", using x (or X) as the only variable, e.g. "3(x-2) = 5x + 4" or "(x+1)(x-3) = 2x^2 - 5". Numbers may be integers or decimals. Implicit multiplication is fine ("3x", "2(x+1)"). Exponents may only be "^2" on the bare variable — "(x+1)^2" is not supported; write "(x+1)(x+1)" instead.
Refuses rather than guesses on: no "=" or more than one, a second variable or a function name (sin, sqrt, log), a "/" anywhere (rewrite as a decimal), an unsupported exponent, an equation that expands past degree 2, unbalanced parentheses, or an inequality (<, >). Every refusal includes a fixHint saying exactly what to change.
Returns the equation type (linear, quadratic, identity, or contradiction), the standard form, the full list of steps, the solution(s) as exact fractions (with a decimal alongside when not a whole number), and a disclaimer that this covers only one-variable linear and quadratic equations.
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | TODO: state the exact format, units, and range. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only mark readOnlyHint=true and openWorldHint=false, so the description supplies the behavioral detail: exact fraction arithmetic, no floating-point guessing, explicit reporting of complex roots, and reliable refusal behavior with fixHint. It also states what the tool returns, including the equation type, standard form, steps, and disclaimer, which the annotations do not cover.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is long but every section earns its place: purpose, usage guidance, failure modes, input syntax, refusals, and return values. The structure is logical and front-loaded, starting with the core operation before moving to constraints. There is no filler or repetition beyond what is useful for an agent.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity, the single schema parameter is underspecified, and there is no output schema, the description covers all necessary ground: what inputs are accepted, what is rejected and why, how numbers are handled, what steps are returned, and the scope limitations. An agent could invoke this tool correctly without additional clarification.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Although the schema reports 100% description coverage, the actual property description is a placeholder: 'TODO: state the exact format, units, and range.' The tool description fully compensates by specifying the single-string format, allowed variables, examples, implicit multiplication, exponent limitations, and exact refusal conditions. This is far more semantic value than the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: it 'Solves a linear or quadratic equation in one variable (x) and returns every step.' It goes beyond a generic statement by naming the equation forms, the output content, and the scope (one variable, degree 2 max), so the tool's purpose is unambiguous even without siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly tells the agent when to use the tool ('Use this whenever you need to solve ...'), and more importantly tells it when not to silently reason: 'Do not solve this kind of equation by reasoning through it token by token.' It also enumerates refusal cases, making the conditions for using or not using the tool explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
runClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Evaluate, simplify, and differentiate mathematical expressions.
Deterministic Sudoku puzzles, progress checks, logical hints, and step-by-step solutions.
Deterministic engineering solvers: biquad filter design, room eigenmodes, LLM VRAM fit.
Precision math engine for AI agents. 203 exact methods. Zero hallucination.
Add one secure layer between your agents and this server.
With only one tool, there is no possibility of an agent mistaking it for another operation. The description clearly scopes the tool to one-variable linear and quadratic equations.
There are no mixed conventions because only one tool exists, but 'run' is a generic verb that gives no hint of the equation-solving domain. A name like solve_equation would align better with the server's purpose.
A single tool feels thin for a general-purpose MCP server, but it is defensible here because the server is narrowly focused on solving one-variable linear/quadratic equations with steps. The scope is coherent rather than bloated.
The tool covers the full promised domain: linear and quadratic equations, identities, contradictions, exact fractions, and complex roots, with explicit refusal hints for unsupported input. No important operation within the stated scope is missing.
