Skip to main content
Glama

Count CSV category combinations

bpj_pivot_csv_counts
Read-onlyIdempotent

Count observed combinations of two columns, such as category and status.

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": {
      "csv": "<csv>",
      "rowKey": "<rowKey>",
      "columnKey": "<columnKey>"
    },
    "name": "bpj_pivot_csv_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYes
rowKeyYes
columnKeyYes

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, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The word 'observed' adds a useful hint that combinations absent from the data are not reported, but nothing is said about output shape, ordering, or handling of large CSVs.

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 short sentence with no filler, and the core concept (counting combinations) is front-loaded. It is efficient, though the brevity borders on under-specification rather than tightness.

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?

With no output schema, three required parameters at 0% schema description coverage, and no annotations gaps to excuse it, the description should explain what the result looks like (a cross-tab of counts) and how the two axis parameters differ. Those gaps leave the agent guessing at call semantics.

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 coverage is 0%, so only the bare titles ('CSV with headers', 'Group column', 'Category column') are available. The description mentions two columns and gives an example pair, but never maps them to rowKey versus columnKey or explains why the ordering of the two axes matters for the result.

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 ('count') and resource ('observed combinations of two columns') plus a concrete example pair (category and status), which clearly separates it from siblings like bpj_csv_to_json, bpj_filter_csv, or bpj_profile_csv. It does not explicitly name a sibling it is not, so it stops short of a 5.

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 guidance on when to choose this over alternatives such as bpj_profile_csv or bpj_filter_csv, and no stated preconditions. The example column pair implies a cross-tabulation use case, but the agent must infer the context entirely.

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.