Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Capital Gains Tax HQ 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.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly does not. It never states that the tool is a read-only lookup, never mentions the 50-row cap enforced by the schema, and says nothing about return shape, ordering ties, or behavior when the column is non-numeric — despite explicitly requiring a numeric column.

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

Conciseness5/5

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

A single sentence, front-loaded with the operation and resource, followed by the question it answers. Nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with no output schema, the definition covers the core purpose and the critical numeric-column constraint. It falls short of complete because the row cap and the result shape are unstated, but the essential calling information is present.

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 coverage is only 33%, and the description does compensate on the most important gap: the undocumented 'column' parameter is constrained to a numeric column, which the schema does not say. The 'highest (or lowest)' phrasing maps onto 'ascending', but the 'limit' parameter and its 50 maximum 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?

The description states a specific operation (return the highest or lowest rows) on a specific resource (the Capital Gains Tax HQ dataset) keyed by a numeric column, and adds an intent gloss ("which is the most/least X"). That is enough to distinguish it from siblings like dataset_search or dataset_stats by intent, though it does not name any alternative explicitly.

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 phrasing "which is the most/least X" implies the question shape it answers, which is useful routing context. However, it gives no when-not guidance, no mention of prerequisites, and no explicit steer to a sibling such as dataset_stats when aggregation rather than ranking is wanted.

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