Skip to main content
Glama

Rank rows by a numeric column

dataset_top

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

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

With no annotations supplied, the description carries the burden, and it does disclose the ordering semantics (descending by default, ascending optional). It does not say the operation is read-only, what the returned row shape looks like, how ties are handled, or that the result set is capped — gaps that matter more given zero annotation coverage.

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 core operation front-loaded and no filler. The nested quotation for the example phrase is slightly awkward to parse but does earn its place as a usage cue.

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 ranking tool with no output schema, the description covers the essential operation and ordering direction. It still leaves the limit parameter and the shape of returned rows unaddressed, which an agent needs to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, with just the ascending parameter documented. The description adds real meaning for column by constraining it to a numeric column, but leaves limit entirely unexplained in both schema and description (no default, no mention of the 50-row ceiling or return-size implications).

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 concrete operation (returning the highest or lowest rows of the HardFM dataset ranked by a numeric column), which is a specific verb+resource. It implicitly differentiates from aggregate-style siblings like dataset_stats by framing the result as rows, but it never explicitly contrasts 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 quoted example "which is the most/least X" gives an implied usage cue for when this tool is the right pick. However, there is no explicit statement of when not to use it or which sibling to prefer for aggregates, column discovery, or filtered searches.

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