Skip to main content
Glama

Rank rows by a numeric column

dataset_top

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

No annotations are provided, so the description carries the full disclosure burden. It implies a read-only retrieval and conveys the asc/desc semantics, but says nothing about limits defaults, the 1-50 cap, tie-breaking for duplicate values, or what the returned rows look like. That is a notable gap for a tool with 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 sentence that front-loads the operation and closes with a natural-language question pattern an agent can pattern-match against. There is no filler, though the quoted example slightly crowds out room for behavioral detail.

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?

With no output schema and no annotations, the description should say more about result shape and default behavior. It is adequate to recognize the tool's intent but leaves the agent guessing on default limit, maximum result size, and how ties are resolved.

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 description coverage is only 33% (only 'ascending' is documented in the schema), so the description should compensate more than it does. It does clarify that 'column' must be numeric and that ascending means lowest-first, but the 'limit' parameter is entirely unaddressed 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?

"The highest (or lowest) rows of the Bags That Pay dataset by a numeric column" names a specific operation (top-N ranking), a specific resource (dataset rows), and the axis of ranking (a numeric column). It is clearly distinct from dataset_row or dataset_search, though the sibling differentiation is implicit rather than stated.

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 question pattern "which is the most/least X" gives a useful intent cue for when this tool applies, which is more than nothing. However, it never states when to prefer a sibling (e.g., dataset_stats for aggregates or dataset_search for non-numeric filtering), so the agent must infer the boundary itself.

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