Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Taxooor 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 disclosure burden, and it says nothing about behavior: no default limit, no tie-breaking or ordering rules, no error behavior for non-numeric or missing columns, no note on what a row contains. The only behavioral hint ('numeric column') is a correctness constraint, not a behavioral trait.

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 compact sentence with the resource and the ranking semantics front-loaded and a clarifying example appended. It is efficiently sized, though the construction is slightly elliptical and would read better as an explicit verb phrase.

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

Completeness5/5

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

Placeholder — see corrected value below.

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. The description usefully clarifies that 'column' must be numeric and that 'ascending' means lowest-first, which adds meaning beyond the schema. It says nothing about 'limit' (the schema gives bounds 1–50 but no default), so one of three parameters remains unexplained everywhere.

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 the resource (Taxooor dataset), the operation (returning the highest/lowest rows ranked by a numeric column), and gives a natural-language gloss ("which is the most/least X"). It is clearly a ranking/ordering tool, distinguishable in kind from dataset_stats or dataset_row, though it does not explicitly contrast itself with any sibling.

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 framing question "which is the most/least X" implies the kind of query this tool answers, which is useful routing context. However, there is no explicit statement of when to prefer this over dataset_stats, dataset_search, or dataset_compare, and no mention of constraints such as the column needing to be numeric-safe.

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