Skip to main content
Glama

Within-group median bands

bpj_table_group_threshold_median_split
Read-onlyIdempotent

Label each measurement as below, at or above its own category median.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes
groupYes
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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds genuinely useful behavior: the split is computed within each category against that category's own median and produces three bands (below, at, above). It does not disclose the resulting shape—whether a label column is added, what the labels are named, or how ties/'at' are determined.

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?

One short sentence with no wasted words and the operative constraint (per-category median) placed where it is read first. It is efficient but so terse that structure beyond a single clause is absent.

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 data-transforming three-parameter tool with no output schema, so the description should explain the return value and the labeling convention. It says nothing about output shape, label naming, ordering, or how missing/non-numeric values are handled, leaving real gaps for an agent that must chain this with other group tools.

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%, so the description must carry the burden, and it only implicitly maps the three required parameters: measurements evidently come from 'column', grouping from 'group', and 'rows' is untouched. It never states that 'rows' is a JSON record array string, that 'column' names the measured field, or what happens to inputs that fail to parse or lack the named columns.

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 ('Label') and resource ('each measurement') and makes the comparison basis explicit ('its own category median'), which distinguishes it in spirit from plain median computation. It stops short of naming a sibling such as bpj_table_group_median, so an agent must infer the distinction from the name and shared context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'its own category median' implies usage: per-group relative classification rather than global thresholds. There is no explicit statement of when to prefer this over bpj_table_group_median, bpj_table_group_quartiles, or bpj_table_group_boundaries, and no prerequisites or exclusions are given.

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.