Skip to main content
Glama

Group medians

bpj_table_group_median
Read-onlyIdempotent

Compute the median measurement independently in each category.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes
groupYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the description does not need to restate safety. It earns credit by clarifying that computation is done independently per category, but says nothing about tie handling, even-count averaging, null/missing values, or what happens with a category of one.

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 or redundancy. It is efficient, though the brevity comes at the cost of the parameter and edge-case detail noted elsewhere.

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 three-parameter, read-only aggregation with no output schema, the description covers the core semantics but leaves the call-shaping details to the schema titles. An agent still has to infer that rows is serialized JSON and which column is numeric, which is a real gap at 0% schema description coverage.

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 compensate, and it does so partially: 'measurement' maps to the column parameter and 'category' maps to the group parameter. It adds nothing about the rows parameter, which is a JSON record array passed as a string with a 12000-character limit, or about accepted value types in the measurement column.

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 ('compute the median measurement') plus the per-category scope, which distinguishes it from bpj_table_group_mean, bpj_table_group_mode, and bpj_table_group_quartiles by statistic alone. It does not name or explicitly exclude any sibling, so sibling routing relies on the shared naming pattern.

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 prerequisite note, and no mention of alternatives such as the mean or quartile group tools. The only usable signal is implied: pick this when the desired summary statistic is a median.

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.