Skip to main content
Glama

Median and IQR scaling

bpj_series_robust_scale
Read-onlyIdempotent

Center values on the median and divide by the interpolated interquartile range.

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": {
      "values": "<values>"
    },
    "name": "bpj_series_robust_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the divisor is an interpolated IQR (a method detail beyond annotations), but says nothing about the response shape, the interpolation convention used, or what happens when the IQR is zero for a constant series — the most likely failure mode of a divide-by-spread transform.

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 sentence with zero filler, front-loading the two operations in the order they are applied. It is efficient, though its brevity edges toward under-specification rather than true concision.

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 deterministic transform the formula is the core content, and it is present, but the definition omits the return value, the interpolation method, empty/short-series handling, and the zero-IQR degenerate case. With no output schema and no annotations covering edge behavior, those omissions leave real gaps.

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?

There is a single required parameter and the description says nothing about it; schema description coverage is 0%. The schema's own title ('Number array (JSON)') and maxLength hint that values arrive as a JSON-encoded string, but the description never confirms the encoding or the size limit, so it does not compensate for the coverage gap.

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?

Names a specific operation: centering on the median and dividing by the interpolated IQR. That formula distinguishes it from the neighboring min-max scaler and MAD-based robust scale far better than the title alone, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The operation implies its use case (outlier-resistant normalization), but there is no explicit when-to-use, no prerequisites, and no mention of when a different scaler such as min-max or median-absolute-deviation would be preferable.

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.