Skip to main content
Glama

First and last values per group

bpj_table_group_boundaries
Read-onlyIdempotent

Return the first and last observed target value in original record order for each key.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes
groupYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds one genuinely useful trait — results follow original record order and only 'observed' values are considered (implying missing values are skipped) — but it says nothing about the output structure or how groups with a single record behave. With annotations carrying the safety profile, this is a moderate-added-value 3.

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, which is efficient. The compactness is appropriate, though the same brevity leaves the parameter and output gaps unaddressed.

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?

For a three-parameter tool with zero schema description coverage and no output schema, the description should map each parameter and indicate the shape of the result (two values per group). It does neither, so significant gaps remain for the agent to fill.

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 schema offers only bare titles ('Record array (JSON)', 'Grouping column', 'Column name'), and the description does not compensate. It never explains that 'group' selects the key column, that 'column' supplies the target value, or what format 'rows' must take beyond JSON, so an agent must guess at input semantics.

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 states a specific verb and result ('return the first and last observed target value ... for each key'), which cleanly separates it from siblings like group_extent or group_cardinality. It loses a point because 'key' is used without tying it to the 'group' parameter or naming any sibling explicitly.

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 statement of when to use this tool versus the many other per-group aggregations (mean, median, extent, quartiles, etc.). The description gives no preconditions, no exclusions, and no alternative routing, leaving the agent to infer usage purely from the name.

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.