Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Trading Card Value Checker 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, the description carries the full behavioral burden. It does add one real behavioral constraint not in the schema: the column must be numeric. But it says nothing about tie-breaking, what happens with a non-numeric column, the default row count, or that this is a read-only operation returning full 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?

A single front-loaded sentence with the ranking behavior stated first; no wasted prose. The nested quotation around the example question is slightly awkward but it does earn its place by clarifying the intended question type.

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 three-parameter query tool with no annotations and no output schema, the description should say what a returned row contains (all columns or just the ranked one) and the default limit. It covers the core ranking semantics but leaves the return shape entirely unstated, which the absence of an output schema makes more costly.

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%: only `ascending` is documented in the schema, and the description merely restates that same highest/lowest distinction. It adds useful meaning for `column` (must be numeric) but never mentions `limit` at all, leaving its default and its role in the response shape undocumented 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?

States a concrete operation: returning the highest or lowest rows of the Trading Card Value Checker dataset ranked by a numeric column, with a plain-language gloss ("which is the most/least X"). The verb+resource combination is clear, but no sibling tool is named or excluded, so differentiation from dataset_stats or dataset_search 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 "which is the most/least X" framing implies the right use case (extremal-value questions), which is genuinely helpful. However, there is no explicit statement of when not to use it, no mention of the aggregation/statistics alternative, and no prerequisites such as the column needing to be numeric are stated as a usage constraint.

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