Skip to main content
Glama

Rolling arithmetic mean

bpj_series_moving_mean
Read-onlyIdempotent

Return one mean for every full trailing window.

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>",
      "width": "<width>"
    },
    "name": "bpj_series_moving_mean"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
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?

The annotations already cover safety traits such as readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful windowing behavior by saying only full trailing windows are returned, but it omits what happens when width exceeds the input length, how output is aligned, and whether partial results are ever emitted.

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 single sentence is front-loaded, direct, and free of filler. It is arguably too terse for a tool with no output schema, but it contains no wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter rolling-mean tool with no output schema, the description states output cardinality ('one mean for every full trailing window') but does not explain input encoding or important edge behavior. It is minimally adequate rather than complete.

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 must compensate for undocumented parameters. It only hints at the width parameter via 'trailing window' and says nothing about the values parameter being a JSON-encoded number array, the 1–500 width bound, or how the two parameters interact.

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 computation: one arithmetic mean per full trailing window. This is clear enough to distinguish it from non-windowed mean tools, but it does not explicitly name or differentiate against siblings such as moving_median or moving_volatility.

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, no comparison to the many moving_* alternatives, and no prerequisites or edge-case conditions. An agent must infer its role from the name and the one-sentence description.

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.