Skip to main content
Glama

Mean-centered deviations

bpj_series_center
Read-onlyIdempotent

Subtract the arithmetic mean from every observation while retaining its units.

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

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is fully covered elsewhere. The description's one contribution beyond that is that units are preserved (i.e., a pure location shift, not a normalization), which is genuinely useful. It does not disclose that the result has the same length as the input or that the output is a numeric array.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single front-loaded sentence with no filler, hedging, or repetition. Every clause contributes distinct information (operation plus the units-preserving property).

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?

The tool is simple and annotations cover safety, but with no output schema and no parameter descriptions, the definition should state the input encoding (JSON array string) and the return shape (an equal-length array of deviations). Neither appears, leaving real gaps for a caller that must construct the argument 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% for the single required parameter, so the description carries full responsibility and provides nothing: it never mentions that "values" is a JSON-encoded array string nor the 12,000-character cap. The only hint at input shape is the generic schema title.

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?

"Subtract the arithmetic mean from every observation" names a specific operation on a specific resource, and "while retaining its units" distinguishes it from scaling siblings such as min_max_scale. It stops short of explicitly differentiating itself from related transforms (e.g., moving_mean or lag_differences), but the verb+resource pairing is unambiguous.

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 guidance at all: no statement of the analytical situation that calls for centering, no prerequisites, and no named alternative among the many series tools. The agent must infer applicability purely from the mathematical definition.

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.