Skip to main content
Glama

Two-dimensional sum pivot

bpj_table_pivot_sums
Read-onlyIdempotent

Sum a numeric measure across two categorical dimensions and fill unobserved combinations with zero.

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>",
      "across": "<across>",
      "column": "<column>"
    },
    "name": "bpj_table_pivot_sums"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
groupYes
acrossYes
columnYes

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, closed-world behavior, so the safety profile is covered. The description adds one genuine behavioral fact beyond that: unobserved row/across combinations are filled with zero rather than omitted. It says nothing about the shape of the returned table or error behavior, which keeps it at a middling score.

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; the core operation comes first and the zero-fill detail follows. It is efficient, though the terseness leaves little room for the context the tool actually needs.

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?

This is a multi-parameter pivot operation with 0% schema description coverage and no output schema. The description omits the expected format of the 'rows' JSON string, the resulting table layout, and any failure modes, so an agent cannot confidently construct a correct call from it alone.

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

Parameters3/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 the semantic load. It implicitly clarifies that 'column' is the numeric measure and that 'group'/'across' are categorical dimensions, but 'rows' — a JSON record array — is never explained in the description, and no guidance is given on how column names are referenced.

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 gives a specific verb and resource: 'Sum a numeric measure across two categorical dimensions.' That distinguishes it from count-based siblings such as bpj_pivot_csv_counts, but it never names or explicitly contrasts an alternative, so it stops short of full sibling differentiation.

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 when-to-use or when-not-to-use guidance. The agent learns what the tool computes but not the conditions that select it over bpj_matrix_direct_sum, bpj_pivot_csv_counts, or the group-mean/median siblings, and no prerequisites or input-format expectations are stated.

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.