Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Taxyearvo 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 exist, so the description carries the full behavioral burden, yet it says nothing about whether the call is read-only, how ties are broken, how non-numeric or null values in the column are handled, or what the result shape is. The only real signal is the implicit parenthetical that setting low values returns the least rows.

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 compact sentence with the core operation front-loaded and no filler. The embedded quoted user question adds intent without bloat, though the phrasing is slightly awkward and the second clause is doing double duty.

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 3 parameters at 33% coverage, an agent still cannot tell how many rows come back by default, what the bound of 50 is applied against, or what happens with duplicate or missing values. For a ranking tool these omissions matter for correct invocation.

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), so the description must compensate and partially does: it conveys that 'column' must be numeric and that high/low maps to sort direction. However, the 'limit' parameter — including its default and 50-row cap — is never mentioned in either the schema or the description.

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 gives a specific verb-plus-resource combination: return the top-ranked rows of the Taxyearvo dataset by a numeric column. The paraphrased user question ('which is the most/least X') makes the intent distinguishable from dataset_search and dataset_stats, though the tool name 'dataset_top' is never spelled out as ranking/sorting.

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 only implied through the example question ('which is the most/least X'), which suggests picking an extreme value. There is no explicit statement of when to prefer this over dataset_search, dataset_stats, or dataset_row, and 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