Skip to main content
Glama

Successive changes within groups

bpj_table_group_successive_change
Read-onlyIdempotent

Subtract the previous target value within each group, leaving its first position null.

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": {
      "rows": "<rows>",
      "group": "<group>",
      "column": "<column>"
    },
    "name": "bpj_table_group_successive_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
groupYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description usefully adds the first-row-null behavior, which an agent could not guess. However, it omits the critical order-dependence of "previous" (rows must already be sorted within groups) and says nothing about non-numeric values or output column naming.

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 tight sentence with the core operation front-loaded and no filler. It is arguably under-specified rather than verbose, but structurally it is clean and easy to scan.

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?

For a three-parameter transformation tool with no output schema and no schema descriptions, the definition leaves too much unstated: input format for rows, sort requirements, numeric handling, and the shape/name of the resulting column. An agent could invoke it but would likely get order-dependent or type-related surprises.

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 largely does not. It implies "group" ("within each group") and loosely gestures at "column" ("target value"), but never explains that rows is a JSON record array supplied as a string, that column must be numeric, or what form group takes. Two of three parameters remain effectively undocumented.

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?

"Subtract the previous target value within each group" states a specific verb (subtract) and the exact transformation (lag-difference), which separates it from siblings like bpj_table_group_running_total or bpj_table_group_demean. The phrase "target value" is slightly loose given the parameter is named "column", but an agent can still identify the operation.

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 statement of when to use this tool versus alternatives, no prerequisites, and no mention of when-not to use it. The agent must infer from the name and one-line behavior that this is the correct choice over running_total, percent_changes, or demean.

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.