Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Medcontra 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 burden. It conveys the core ranking behavior and direction, but says nothing about the default row count, how ties are broken, ordering of the returned rows, or what happens if the named column is non-numeric or missing — the main failure modes for a ranking tool.

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 sentence with the key semantics (direction + ordering column) front-loaded and no filler. The nested colon-and-quote construction is slightly awkward but does not cost the agent comprehension.

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 and no annotations, the definition covers the essentials of ranking but leaves default/maximum result size and the shape of the returned rows unstated. Adequate, but an agent would still have to probe to know what it gets back.

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 33%: only 'ascending' is documented in the schema, and the description reinforces the highest/lowest meaning. It also adds a constraint the schema lacks — that 'column' must be numeric (the schema only says string). The 'limit' parameter is left entirely unaddressed, so compensation is partial.

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 verb and resource: returning the highest or lowest rows of the Medcontra dataset ordered by a numeric column. The quoted example ('which is the most/least X') makes the intent concrete. It does not name any sibling (dataset_row, dataset_search, dataset_stats) to differentiate itself 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 'which is the most/least X' framing implies the class of question this answers, which is real usage guidance. However, it never states when to prefer it over dataset_search, dataset_stats, or dataset_compare, and gives no exclusions or prerequisites.

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