Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Crypto Exchange Compare HQ 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?

With no annotations, the description carries the full burden; it does disclose the core behavior (sorted ranking with optional reversal to lowest values) and that the ranking column must be numeric. It omits other behaviorally important details: the default and maximum row count, tie-breaking, and how non-numeric or missing values are handled.

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 a short illustrative gloss; nothing is padded. The phrasing 'the highest (or lowest) rows' is slightly compressed but still clear.

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 tool with no annotations and no output schema, the description should say more about the returned shape (full rows vs. selected fields) and the limit semantics, especially since the 50-row cap appears only in the schema.

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% — only 'ascending' is documented in the schema. The description adds real meaning by clarifying the sort column must be numeric and that the direction can be inverted, but the 'limit' parameter is undocumented in both places, so the gap is only partially closed.

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/lowest rows) on a specific resource (the Crypto Exchange Compare HQ dataset) ranked by a numeric column, and gives a natural-language gloss of the question shape ('which is the most/least X'). It does not distinguish itself from siblings such as dataset_stats or dataset_search, so it stops 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?

The phrase 'which is the most/least X' implies the question type this tool answers, which is useful context for selection. However, there is no explicit when-not guidance and no named alternative for cases like aggregation (dataset_stats) or filtering (dataset_search), so the agent must infer routing.

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