Skip to main content
Glama

Theil-Sen robust line

bpj_pairs_theil_sen
Read-onlyIdempotent

Estimate a robust line using the median nonvertical pair slope and median point intercept.

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

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 readOnly, idempotent, closed-world, non-destructive, so safety is covered. The description adds method-level detail (median of pairwise slopes, median intercept), which usefully signals a deterministic, outlier-resistant computation, but says nothing about the returned quantities, minimum sample size, or how ties/degenerate x-values 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.

Conciseness4/5

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

A single well-formed sentence with the method detail front-loaded and no filler. It is arguably too terse for the gaps it leaves, but nothing in the text is wasted.

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 estimator with no output schema and no parameter documentation, the description should state input alignment requirements, minimum pair count, and what is returned (slope and intercept). None of that is present, so an agent cannot determine correct invocation from the 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%; the only guidance is the property titles "First numeric series (JSON)" and "Second numeric series (JSON)". The description contributes nothing about what x and y are, that they must be equal-length and index-aligned, or the JSON encoding, so the 0% coverage is not compensated.

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 ("Estimate") and resource ("a robust line") and even names the estimator mechanism (median nonvertical pair slope, median point intercept), which distinguishes it from a plain fit. It never names or contrasts with the closest sibling (bpj_pairs_linear_fit), so an agent must infer that differentiation from the name alone.

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, and no alternative is named. The robust-regression framing implies the OLS sibling should be avoided when outliers are present, but that is left entirely to inference.

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.