Skip to main content
Glama

Group ranges and bounds

bpj_table_group_extent
Read-onlyIdempotent

Return the minimum, maximum and range for each 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_extent"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
groupYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. Beyond that the description adds nothing: it does not say whether the range is max−min, how groups are ordered, what happens with nulls or non-numeric columns, or whether the result is one row per group.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words, but the brevity comes at the cost of under-specification rather than efficiency. There is no structure beyond the one clause.

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 three required parameters at 0% schema coverage and no output schema, the description should explain input encoding and the shape of the returned statistics. Neither is present, leaving an agent to guess how to serialize `rows` and how to read the per-group min/max/range result.

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 compensate, and it largely does not. Only the phrase "for each group" hints at the roles of `group` and `column`, while the critical fact that `rows` is a JSON-encoded record array string (max 12,000 chars) is left entirely to the terse schema titles.

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?

"Return the minimum, maximum and range for each group" names a specific computation and the grouping granularity, which separates it from siblings like bpj_table_group_mean, bpj_table_group_median and bpj_table_group_quartiles. It does not explicitly contrast with the closest neighbours, bpj_table_group_boundaries and bpj_table_group_dispersion, whose scope overlaps with min/max/range.

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 gives no when-to-use guidance, no prerequisites, and no named alternative for the boundary case (bpj_table_group_boundaries). The only implicit signal is "for each group", which tells the agent the operation is grouped but not when this tool beats its siblings.

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.