Skip to main content
Glama

Quadratic Regression

calculator_quadratic_regression
Read-only

Fit y = ax² + bx + c with R² and optional prediction.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "calculator_quadratic_regression"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX data.
yYesY data.
predict_xNoOptional prediction X.

Output Schema

NameRequiredDescriptionDefault
aYes
bYes
cYes
equationNo
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that the fit reports R² and that prediction is optional, which is modest extra value. It does not mention constraints such as the minimum number of data points required for a 3-parameter fit or how mismatched x/y lengths are handled.

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?

A single compact sentence that front-loads the model and appends the notable outputs. Nothing is redundant and nothing is buried.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. However, for a regression tool with two required array parameters, the description omits the one thing an agent can get wrong: the minimum sample size (at least 3 points for a quadratic) and pairing/equal-length expectations for x and y.

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 description coverage is 100% and each parameter carries its own description plus examples, so the schema does the heavy lifting. The description only confirms that predict_x is optional, which is already visible from the schema's required list; baseline 3 applies.

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?

The description names a specific operation and its mathematical model (fit y = ax² + bx + c), plus two distinguishing outputs (R² and optional prediction), so an agent knows exactly what is computed. It stops short of explicitly contrasting with near-neighbors like calculator_linear_regression, calculator_regression, or calculator_polynomial, which is the only thing keeping it from a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing says to pick this over calculator_linear_regression or calculator_polynomial when the data trend is ambiguous. The only hint is the word 'optional' for prediction, which is a parameter note rather than routing advice.

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.