Skip to main content
Glama

Symmetric absolute percentage error

bpj_pairs_symmetric_error
Read-onlyIdempotent

Scale errors by the sum of absolute actual and forecast values, treating a double zero as zero error.

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

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 establish that this is a safe, read-only, idempotent computation, so the description need not cover safety. It adds useful behavioral detail by specifying the scaling formula and the double-zero edge case. However, it does not describe the return value, whether results are scalar or per-pair, or any assumptions about input alignment.

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 description is a single front-loaded sentence with no wasted wording. It communicates the formula and an important edge case efficiently. It could be slightly clearer by naming the metric or input roles, but it is appropriately concise.

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 metric computation with no output schema and 0% schema description coverage, the definition is incomplete. It omits which parameter is actual versus forecast, how the JSON series strings are structured, and what the output looks like. Those gaps matter for calling the tool correctly.

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 carries the burden of explaining the parameters. It mentions actual and forecast values but never maps them to x and y, nor explains that the inputs are JSON-encoded numeric series. The schema titles identify x and y as numeric series, but the critical actual-vs-forecast assignment remains ambiguous.

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 states a specific metric behavior: scaling errors by the sum of absolute actual and forecast values. That plus the title makes clear it computes a symmetric percentage-error variant. It does not explicitly distinguish itself from nearby siblings such as bpj_pairs_percentage_error or bpj_pairs_absolute_error, but the formula provides implicit differentiation.

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 guidance on when to use this metric instead of alternatives like percentage error, absolute error, or RMSE. The double-zero handling implies a forecasting context, but it does not state when this measure is preferred or inappropriate.

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.