Skip to main content
Glama

Rolling median filter

bpj_series_moving_median
Read-onlyIdempotent

Smooth isolated spikes with the median of each 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_median"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
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, and closed-world, so the safety profile is covered. The description adds one real behavioral fact beyond that: only "full" windows are used, implying the leading width-1 positions produce no output and the result is shorter than the input. It does not state the return shape or how short series are handled.

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 well-formed sentence with no filler, and the smoothing purpose is front-loaded ahead of the mechanism. It is efficient, though borderline under-specified rather than overly verbose.

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 two required parameters, zero schema description coverage, and no output schema, the description is the only explanatory layer and it supplies one sentence. An agent can guess the operation but cannot determine output length, edge-case behavior, or how to encode the values parameter from this text alone.

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 full burden for two required parameters. It clarifies window alignment ("trailing", "full") but not the width semantics beyond that, and says nothing about values being a JSON-encoded number array, the 1-500 width bound, or behavior when width exceeds series length.

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?

"Median of each full trailing window" states a specific computation and its alignment, and "smooth isolated spikes" names its intended effect. It implicitly distinguishes itself from bpj_series_moving_mean by using a median, but it never names that sibling, so an agent must infer the contrast from the tool name.

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 phrase "smooth isolated spikes" implies the use case (outlier-resistant smoothing) and thereby hints at when a median beats a mean. However, no alternatives are named and no when-not-to-use condition or prerequisite (e.g., minimum series length relative to width) is given.

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.