Skip to main content
Glama

site

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the DoorsetBook 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?

With no annotations, the description carries the full burden of behavioral disclosure and falls well short. It does not say whether full rows or only the ranked column are returned, what the default row count is, how ties or nulls in the ranking column are handled, or whether the column must exist and be numeric (it says 'numeric column' but not what happens otherwise).

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?

One sentence, front-loaded with the core operation and the resource, with the example question appended as a clarifying gloss. No filler, though the phrasing is slightly compressed and the quoted example reads awkwardly.

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 simple three-parameter read tool with no output schema, the definition covers what it does but omits the two things an agent most needs to call it well: what the response shape looks like (full rows vs. ranked values) and the default/limit behavior. Adequate but with clear gaps.

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% — just 'ascending' is documented in the schema. The description does add genuine meaning by stating the ranking column must be numeric (the schema only types it as a string) and by framing highest-vs-lowest ordering, but it says nothing about the 'limit' parameter, its default, or its 1–50 bound.

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 names a specific operation (return the highest/lowest rows) on a specific resource (the DoorsetBook dataset) keyed by a numeric column, and the quoted 'which is the most/least X' framing pins down the intent. It is clearly distinct from stats, search, or column-listing siblings, though it never names an 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?

Usage is implied by the example question ('which is the most/least X'), which is a real signal about when to reach for this tool. However, there is no explicit when-not guidance, no mention of when dataset_stats or dataset_search would be better, and no prerequisite or ordering caveats.

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