Skip to main content
Glama

quadratic_solve

Read-onlyIdempotent

Solve quadratic equations ax² + bx + c = 0 to get roots, discriminant, and vertex from coefficients a, b, and c.

Instructions

Solve a quadratic equation ax^2 + bx + c = 0. Returns roots, discriminant, and vertex.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "a": "<a>",
      "b": "<b>",
      "c": "<c>"
    },
    "name": "quadratic_solve"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesCoefficient a (must not be 0).
bYesCoefficient b.
cYesCoefficient c.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine value by naming the outputs (roots, discriminant, vertex), which is the key behavioral fact for a tool with no output schema. It does not say what happens when the discriminant is negative (real vs. complex roots), the one remaining behavioral ambiguity.

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

Conciseness5/5

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

Two short sentences with no filler: the operation first, the return payload second. Everything is front-loaded and nothing is repeated from structured fields.

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 3-parameter pure-computation tool with no output schema, the description supplies the equation form and the return values, which is nearly everything an agent needs. The gap is behavior when a=0 is rejected or when the discriminant is negative, neither of which is addressed.

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 100% and already documents a, b, c, including the 'a must not be 0' constraint. The description ties the three parameters to the standard quadratic form, which is a modest clarification but does not add syntax or range information beyond the schema. Baseline 3 applies.

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?

Names a specific operation (solve) on a specific object (quadratic equation ax^2+bx+c=0), and disambiguates from nearby siblings such as linear_solve, polynomial_ops, and standard_form. An agent can pick this without opening the schema.

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?

The written-out equation implies when the tool applies, but there is no explicit statement of alternatives (e.g., linear_solve for degree 1, root_find for general roots) or of edge conditions. Usage must be inferred from the formula rather than stated.

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