Skip to main content
Glama

Lagged differences

bpj_series_lag_differences
Read-onlyIdempotent

Subtract the earlier observation from each value at the requested lag.

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>",
      "lag": "<lag>"
    },
    "name": "bpj_series_lag_differences"
  }
}

Input Schema

NameRequiredDescriptionDefault
lagYes
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 establish that the tool is read-only, idempotent, and non-destructive. The description adds the core behavior, but it does not disclose output length, handling of initial observations, or behavior near the maximum lag.

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 description is a single front-loaded sentence with no wasted wording. It is highly concise, though the resulting brevity leaves important operational details for other sections to cover.

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 simple two-parameter computation with rich safety annotations, the purpose is understandable. However, with no output schema and 0% schema description coverage, the definition remains thin on input format and return behavior.

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 needs to carry more of the parameter burden. It hints that 'lag' refers to an earlier observation, but it does not explain input JSON encoding, lag bounds, or how the output aligns with the input array.

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 operation: subtract the earlier observation from each value at a requested lag. This clearly identifies a lagged-difference transform, though it does not explicitly contrast it with nearby alternatives such as percent changes or cumulative sums.

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?

The description explains the computation but gives no explicit when-to-use guidance, prerequisites, or exclusions. It does not tell the agent when lagged differences are preferable to related series operations.

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.