Skip to main content
Glama

Equal-variance orthogonal regression

bpj_pairs_deming
Read-onlyIdempotent

Fit a Deming line with equal measurement error variance on both axes.

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_deming"
  }
}

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add modeling context. It does add the key behavioral fact that error variance is assumed equal on both axes, but says nothing about the returned quantities, required equal-length inputs, or failure behavior for mismatched series.

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 filler or redundancy. It is efficient, though its brevity borders on under-specification for a statistical tool rather than being a structural flaw.

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 regression tool with no output schema, the description should clarify what is produced (slope, intercept, variance estimates) and input constraints. Instead it only names the model, so an agent cannot predict the response shape or handle input errors from this definition alone.

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% and only the titles ('First numeric series (JSON)', 'Second numeric series (JSON)') hint at format. The phrase 'both axes' loosely maps x and y to the two measurement axes, but the description never states that inputs are JSON-encoded strings, that they must be equal length, or how pairing works, leaving most parameter meaning undocumented.

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 gives a specific verb+resource ('Fit a Deming line') and a distinguishing model constraint ('equal measurement error variance on both axes'), which separates it from sibling regression tools like bpj_pairs_linear_fit or bpj_pairs_weighted_variance. It does not explicitly name which sibling to use instead, keeping it below 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 guidance, no mention of prerequisites or alternatives, and no signal about when equal-variance Deming is preferred over the many other bpj_pairs_* regression variants. The agent must infer everything about selection from the statistical term alone.

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.