Skip to main content
Glama

Value frequency tables by group

bpj_table_group_value_frequency
Read-onlyIdempotent

Build a frequency table for target values separately inside every group.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes
groupYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is fully covered elsewhere. The description adds nothing beyond a restatement of purpose: with no output schema, it never says what the result looks like (per-group value/count pairs?), whether ordering or ties are defined, or how the inline JSON 'rows' payload is expected to arrive.

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 — every word is doing work. The brevity is close to under-specification, but nothing stated is redundant or bloated.

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 three-parameter, all-required data-transformation tool with no output schema and zero schema description coverage, the definition is thinner than the complexity warrants: it leaves the rows payload format and the return shape undocumented. The annotations carry the safety profile, but the calling contract is only half-described.

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% — the three parameters carry only titles ('Record array (JSON)', 'Grouping column', 'Column name'). The description does implicitly map 'target values' to the column parameter and 'inside every group' to the group parameter, adding real meaning. But it says nothing about the rows parameter, the 12000-character JSON-string form of the data, or the 160-character limits, so the compensation is partial.

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 resource: builds a frequency table of target values, computed separately within each group. That is concrete enough to picture the operation, but it never names the parameters ('column' and 'group') explicitly and never distinguishes itself from nearby siblings such as bpj_table_group_cardinality or bpj_table_group_mode, which an agent could easily confuse with a per-group frequency count.

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 contains no when-to-use guidance, no exclusions, and no mention of alternative tools for similar per-group aggregations. The agent must infer from the name alone that this is the counting variant rather than cardinality, mode, or presence.

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.