Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Dispatchzo 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.1/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 burden. It never says the operation is read-only, how ties are broken, what happens if the column is non-numeric or missing, or what the result shape is (rows vs. a single value). Only the implicit 'read' framing is conveyed.

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 tight sentence with the core concept front-loaded and no filler. The trailing example question earns its place by disambiguating intent.

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

Completeness2/5

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

With no annotations, no output schema, and only a third of parameters documented, the description should say more: it omits the limit parameter entirely, gives no return format, and says nothing about error conditions for a non-numeric column.

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 compensates for 'column' by stating it must be numeric, which is real added meaning, but 'limit' is never mentioned in the description and its 1-50 bound is only visible as a schema constraint.

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 or lowest rows) on a specific resource (the Dispatchzo dataset) qualified by a numeric column, and the quoted example question 'which is the most/least X' pins down the intent. It does not name any sibling, so differentiation is left to inference.

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 quoted question pattern implies the use case (extremes / ranking questions) but there is no explicit statement of when to prefer this over dataset_stats or dataset_search, nor any prerequisites such as the column needing to be numeric.

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