Skip to main content
Glama

Rolling population volatility

bpj_series_moving_volatility
Read-onlyIdempotent

Measure local volatility as population standard deviation in each full 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_volatility"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description's job is to add semantics — and it does: 'population' specifies ddof=0 rather than sample standard deviation, and 'each full window' signals that partial trailing windows are dropped, affecting output length. It omits what happens when values is shorter than width or how output is aligned to input.

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 front-loaded sentence with no filler; every clause carries information. It is arguably too terse for the gaps it leaves, but nothing is wasted or buried.

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 numeric transform with full annotation coverage and no output schema, the core semantics (population std, full windows) are present. Missing are the input encoding expectation, output length/alignment, and short-input behavior, which an agent would need to call it 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 must carry parameter meaning, and it does not: neither 'values' (a JSON-encoded number array) nor 'width' is explained beyond the passing phrase 'each full window'. An agent gets only the bare titles and bounds from the schema.

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?

States a specific verb and resource ('measure local volatility as population standard deviation in each full window'), which distinguishes it statistically from siblings like moving_mean or moving_median. It stops short of naming an alternative, but the statistic itself 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 Guidelines3/5

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

The phrase 'each full window' implies the tool is for windowed rolling analysis rather than one-shot dispersion, which hints at when to use it. There is no explicit when-to-use or when-not-to-use guidance relative to the many other dispersion siblings (median_absolute_deviation, relative_spread, robust_scale).

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.