Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Roofing Quotes UK 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.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only row query, but says nothing about the 50-row cap, default limit, how ties or nulls are handled, or what the returned rows look like — all behavioral facts an agent would want before calling.

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, front-loaded with the operation and resource, with no filler. The trailing illustrative phrase after the colon reads slightly awkwardly but takes no real space.

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

Completeness2/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 leaves too much unsaid: default ordering, the row cap, tie-breaking, and the shape of the result. An agent could call it, but only by guessing at several behaviors.

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%, so the description has a real gap to fill. It does add one meaningful constraint the schema lacks — the column must be numeric — and its 'highest (or lowest)' phrasing maps onto the ascending flag, but the limit parameter and its maximum of 50 are never mentioned anywhere.

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 states a concrete operation (return the highest or lowest rows of the Roofing Quotes UK dataset ranked by a numeric column) and pairs it with a natural-language use case. It is specific about verb and resource, but never distinguishes itself from siblings like dataset_stats or dataset_compare, which an agent could plausibly reach for the same question.

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?

Usage is only implied through the quoted user phrasing "which is the most/least X", which does signal the intended question shape. There is no explicit when-to-use, no when-not-to-use, and no named alternative for related ranking or aggregation questions.

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