Skip to main content
Glama

Simple least-squares fit

bpj_pairs_linear_fit
Read-onlyIdempotent

Fit the second series to the first with a slope, intercept and fitted response per row.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety and repeatability are covered. Beyond those annotations, the description discloses that the result includes a slope, intercept, and per-row fitted response, which is useful output context. It does not disclose assumptions such as ordinary least squares, handling of unequal series lengths or non-numeric JSON, or the structure of the returned rows.

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?

The definition is a single front-loaded sentence with no filler, so it is efficiently sized. The trailing list of outputs ('slope, intercept and fitted response per row') is slightly dense but still readable; the issue is compression rather than wasted words.

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?

For a simple two-parameter regression tool with rich annotations but no output schema, the description covers the core operation and names the returned quantities. However, it omits the input JSON and equal-length expectations and does not specify the shape of the per-row fitted response, so an agent must rely on schema titles and inference.

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 0% and the two parameters are only titled 'First numeric series (JSON)' and 'Second numeric series (JSON)', so the description's orientation ('second series to the first') adds real meaning by indicating y-on-x rather than x-on-y. It still does not explain JSON array format, the equal-length requirement, or how non-numeric/null values are treated, so it only partially compensates for the low schema coverage.

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 concrete operation ('Fit') and the two data roles ('second series' to 'first') and lists the produced quantities ('slope, intercept and fitted response per row'). That is enough to identify a regression routine, but it does not distinguish this tool from sibling fit methods such as bpj_pairs_deming, bpj_pairs_theil_sen, or bpj_pairs_segment_slopes.

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 explicit when-to-use or when-not-to-use statement, and no alternative tool is named. The phrase 'fit the second series to the first' implies an asymmetric y-on-x regression, but it does not tell an agent when this least-squares fit is preferable to the many other bpj_pairs_* regression and correlation tools.

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.