Skip to main content
Glama

Period-to-period percent changes

bpj_series_percent_changes
Read-onlyIdempotent

Compute adjacent percentage changes relative to the previous observation, returning null for a zero base.

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

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description does add one genuine behavioral detail beyond annotations — null output when the base is zero — but says nothing about output length, ordering, rounding, or how non-numeric input is handled.

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 sentence with the core computation front-loaded and the edge-case rule trailing. Nothing is redundant or padded.

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 one-parameter, no-output-schema tool, the description covers the operation and one edge case. It still leaves the agent to infer the input is a JSON-encoded array string and does not describe output shape (n-1 values), which matters for wiring results into a pipeline.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the schema's own title 'Number array (JSON)' plus the description's 'relative to the previous observation' together tell the agent the input is an ordered numeric array where sequence matters. That ordering semantics is the key non-obvious meaning, though the JSON-string encoding requirement is left to the schema title alone.

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 computation: 'Compute adjacent percentage changes relative to the previous observation.' That clearly separates it from siblings like cumulative_sum or period_growth, though it never names an alternative explicitly.

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 'adjacent percentage changes relative to the previous observation' implies the use case (ordered series, consecutive comparisons), but there is no explicit when-to-use, when-not, or pointer to a sibling such as period growth or cumulative share.

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.