Skip to main content
Glama

Root mean squared prediction error

bpj_pairs_rmse
Read-onlyIdempotent

Summarize prediction errors with a quadratic penalty in the original units.

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": "bpj_pairs_rmse"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare a safe read-only, idempotent, non-destructive, closed-world operation. The description adds that errors receive a quadratic penalty and results stay in original units, which usefully signals outlier sensitivity, but it omits mismatched-length handling, missing-value behavior, and return shape.

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 front-loaded sentence with no unnecessary repetition. Its weakness is under-specification rather than verbosity.

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

Completeness2/5

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

For a two-parameter statistical tool with no output schema, the definition is missing critical calling details: parameter roles, JSON-array format expectations, length matching, and expected return. Annotations cover safety but not the computational contract.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it does not clarify that x and y are paired numeric series, which one is prediction versus actual, or that their lengths must match. The schema titles only say 'first/second numeric series (JSON)'.

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 that it summarizes prediction errors with a quadratic penalty in original units. The quadratic/original-units phrasing distinguishes it from absolute-error and percentage-error siblings, though it never explicitly says it computes RMSE or that it compares two paired series.

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?

Offers no when-to-use guidance, no comparison to alternatives such as absolute or percentage error, and no prerequisites about equal-length paired inputs. Usage is only implied by the phrase 'prediction errors'.

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.