Skip to main content
Glama

R-squared against the observed mean

bpj_pairs_forecast_skill
Read-onlyIdempotent

Evaluate supplied predictions against the constant observed-mean baseline using R-squared.

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

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 readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuine behavioral value by naming the exact baseline (constant observed mean) rather than a generic R-squared, but it says nothing about return shape, handling of mismatched series lengths, or errors on non-numeric input.

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?

One front-loaded sentence with no filler, and the metric definition comes before any qualifiers. It is efficient, though its brevity leaves the ordering ambiguity unaddressed rather than being a wording problem.

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?

With no output schema, no parameter descriptions, and a dense sibling namespace of pair metrics, the description should explain the return value and the x/y roles. It covers only the metric definition, which is not enough for an agent to call this correctly on the first attempt.

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 clues are titles calling both parameters 'numeric series (JSON)'. The description mentions 'predictions' and 'observed' but never maps those roles to x and y, leaving the single most important invocation detail — argument order — unresolved.

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 and computation: evaluate predictions against a constant observed-mean baseline using R-squared. This is clearer than a bare name like 'forecast_skill', but it never distinguishes itself from the many sibling pair metrics (bpj_pairs_rmse, bpj_pairs_linear_fit, bpj_pairs_pearson) that also score prediction quality.

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 guidance on when this metric is the right choice versus the sibling alternatives, nor on prerequisites such as equal-length series or matched ordering. The agent must infer the use case entirely from the metric name.

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.