Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the WallChartBook 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?

With no annotations at all, the description carries the full behavioral burden, yet it discloses almost nothing: no indication of what a returned row contains, no mention of the default or maximum result count, no tie-breaking or null handling, and no read-only safety framing. The only behavioral hint, 'default highest first', is already duplicated by the schema's ascending description.

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 resource and purpose front-loaded and no filler. The phrasing is slightly elliptical (the quoted question fragment dangles), but nothing is wasted.

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-only ranking tool with no output schema and no annotations, the description conveys the core concept adequately. It still leaves an agent guessing about default result count, output shape, and behavior on non-numeric or missing values.

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%, with only ascending documented. The description compensates partially by stating that the ranking column must be numeric, which is genuine meaning not present in the schema. However, limit (bounded 1-50) and the required column's expected format are never addressed, so the low coverage is only half offset.

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 (return the highest or lowest rows ranked by a numeric column) on a named dataset, and the natural-language gloss 'which is the most/least X' pins down the intent. It does not explicitly contrast itself with siblings like dataset_row or dataset_stats, so it falls just short of a 5.

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 does suggest a superlative-lookup scenario. There is no statement of when not to use it, nor any pointer to alternatives such as dataset_stats for aggregates or dataset_search for lookups.

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