Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Fair Odds Calculator dataset by a numeric column: "which is the most/least X".

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": {
      "column": "<column>"
    },
    "name": "dataset_top"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
columnYes
ascendingNotrue for the lowest first; default highest first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden and does little with it: it never says what a row result looks like, whether ties are broken deterministically, what the default limit is, or what happens when the named column is non-numeric or missing. Only the ordering direction is conveyed, and that is already restated by the ascending parameter's own schema description.

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; the parenthetical alternatives and the quoted example question are compact and each carries information. The nested quotation marks make it slightly awkward to read but nothing is wasted.

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, non-destructive read tool with no output schema, the definition covers what the tool selects but not what it returns (row objects? which fields? how many by default). The numeric-column constraint is a real addition, but an agent still has to guess at output shape and default behavior.

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 only 33% (column and limit are undocumented), so the description has to compensate. It does add one genuinely valuable constraint not present in the schema: the column must be numeric. It also clarifies that highest-first is the default direction, though ascending's schema description already covers that. The limit parameter and its 50-row ceiling are left entirely to the schema.

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 operation (return the highest/lowest rows ranked by a numeric column) on a specific resource (the Fair Odds Calculator dataset), and the quoted 'which is the most/least X' frames the intent clearly. It does not name or contrast any sibling tool, so an agent must infer that dataset_search or dataset_stats are different, but the operation itself is unambiguous.

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 'which is the most/least X' phrase implies the question shape this tool answers, which is useful usage framing. There is no explicit when-not guidance, no mention of alternatives such as dataset_stats or dataset_search, and no prerequisites or caveats stated.

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.

Resources