Skip to main content
Glama

Top records including cutoff ties

bpj_table_top_with_ties
Read-onlyIdempotent

Keep the largest requested number of rows and any additional ties at the cutoff.

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>",
      "column": "<column>",
      "n": "<n>"
    },
    "name": "bpj_table_top_with_ties"
  }
}

Input Schema

NameRequiredDescriptionDefault
nYes
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 closed-world scope, so safety is covered. The description does add real behavioral value by disclosing that output row count can exceed n because cutoff ties are retained, which an agent could not guess. It does not explain how ties are determined (presumably equal values in the ranking column) or how ordering affects the result.

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 that states the core rule with zero padding. It is efficient, though it is arguably too terse given the 0% schema coverage it must compensate for.

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 three-parameter, no-output-schema transformation, the definition covers the defining tie behavior but leaves the ranking column, sort direction, and expected return shape unaddressed. An agent could call it, but only by guessing at the semantics of column.

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 partially does: 'requested number of rows' maps to n, and 'cutoff' gestures at the ranking column. The critical parameter, column, is never identified as the field used to rank rows, and rows is not described as a JSON-encoded record array, leaving all three parameters semantically thin.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'keep' plus 'rows' with a tie-inclusive cutoff describes a top-N-with-ties operation, which is a recognizably distinct behavior from the sibling table transforms. However, it never states that rows are ranked by the values in a named column, nor the sort direction, so the agent must infer that 'largest' means 'sorted descending by column'. That missing anchor keeps it at vague-but-inferable rather than specific.

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 guidance on when to choose this over alternatives such as dedupe-by-key or grouping tools, and no statement of prerequisites or exclusions. The description only says what is kept, leaving selection entirely to inference 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.