Skip to main content
Glama

Distinct values per group

bpj_table_group_cardinality
Read-onlyIdempotent

Count distinct scalar values in each group and list them in first-seen order.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes
groupYes
columnYes

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?

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value by disclosing the output shape (per-group listing in first-seen order), which matters because there is no output schema. It says nothing about how missing/non-scalar values are treated or how groups are ordered relative to each other.

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. It is efficient, though slightly terse for a tool with three undocumented parameters.

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 aggregation tool whose annotations already carry the safety profile, the core behavior and result ordering are stated. However, with no output schema and 0% schema description coverage, the definition leaves the input format, output record shape across multiple groups, and edge-case handling implicit.

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% and the only text in the schema is bare titles, so the description must compensate, and it does not. It never explains that 'rows' is a JSON record array, that 'group' and 'column' are column-name strings, or what happens on a size overflow near the 12000 maxLength. The phrase 'in each group' only loosely gestures at the group parameter.

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 concrete verb and resource: count distinct scalar values per group and list them in first-seen order. This is clear enough to act on, but it does not distinguish itself from close siblings such as bpj_table_group_value_frequency, bpj_table_group_mode, or bpj_relation_cardinality, so the agent must infer the difference.

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 guidance, no exclusions, and no named alternative. The sentence describes the operation but never says which situations call for cardinality rather than value_frequency or mode.

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.