Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Perdiemo 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
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It does convey the core ordering semantics and that only numeric columns are valid, and phrases the operation as a read. It omits important behavior: the default result size, the maximum of 50 rows, tie-breaking rules, and what happens if the named column is non-numeric or missing.

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 front-loaded sentence with the core capability stated first, followed by the practical question pattern it answers. No padding or redundant restatement of the tool name; the only minor cost is the unexplained reference to 'Perdiemo'.

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?

The tool is simple (three parameters, no output schema, no nesting), so the description does not need to explain return values. Still, an agent cannot tell from the definition how many rows come back by default, what the 50-row cap is, or how the ranked rows are shaped, which matters for planning a call.

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%, with just the 'ascending' parameter documented. The description compensates partially by saying the column must be numeric, which is real guidance the schema lacks, but it never mentions the 'limit' parameter at all, leaving one of three parameters unexplained in both places.

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 (returning the highest/lowest rows) on a specific resource (the Perdiemo dataset), keyed by a numeric column, which is far more than a restatement of the name. It does not explicitly contrast with siblings like dataset_stats or dataset_row, so an agent must infer the boundary, but the operation itself is unambiguous.

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 example 'which is the most/least X' gives a clear usage cue for natural-language ranking questions. However, there is no explicit statement of when not to use it, no mention of alternatives such as dataset_stats or dataset_search, and no prerequisites for when ranking is appropriate versus filtering.

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