Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Kbasevo 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.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it discloses only the ranking direction as the core behavior. It does not state the default row count or the cap of 50 rows, tie-breaking behavior, handling of nulls or non-numeric columns, or whether whole rows or just the ranked values are returned. Read-only nature is strongly implied by "top" but never made explicit.

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 tight sentence plus a natural-language usage phrase, with the core behavior front-loaded. Nothing is padded, though the quoted example is doing double duty as the only usage guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 tool with no output schema and no annotations, the description is nearly adequate: purpose and ranking direction are clear. The remaining gap is the unmentioned limit parameter and return shape, which an agent must infer from the schema alone.

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%: only ascending is documented in the schema. The description does add meaning for column by specifying it must be numeric, which the schema does not say. However, the limit parameter is never mentioned in the description and its 1-50 range and default are left unexplored, so the description only partly compensates for the coverage gap.

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?

Names a specific operation and resource: returns the highest or lowest rows of the Kbasevo dataset ranked by a numeric column. The phrase "which is the most/least X" pins down the question it answers, which implicitly separates it from dataset_search and dataset_stats, though no sibling is named.

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 "which is the most/least X" framing gives an implied usage context, so an agent can tell this is for ranked extreme-value questions. It does not state when to prefer it over dataset_search or dataset_stats, nor any exclusions or prerequisites.

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