Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Sell My Business Quotes 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 (returns ranked rows, direction reversible) and the implicit read-only nature of the query. It omits behavior an agent would want: the default limit, the maximum of 50, tie-breaking, and what happens if the column is non-numeric or absent.

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 efficient sentence that front-loads the operation and appends a natural-language usage cue. Slightly awkward punctuation with the nested colon, but nothing is wasted.

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 read tool with no output schema and no annotations, the basics are covered but the return shape (full rows vs. the single column) and the limit parameter's role remain unspecified. An agent could call it, but would be guessing on paging and output.

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 to compensate. It does add meaning for 'column' (must be numeric, defines the ranking key) and for direction ('highest or lowest'), but 'limit' is never mentioned anywhere and no value format or default is given.

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 Sell My Business Quotes dataset), keyed on a numeric column. That is enough to distinguish it from dataset_stats or dataset_search in spirit, though it never names a sibling or states the boundary explicitly.

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 paraphrase 'which is the most/least X' gives an implied trigger condition that maps well to real questions, which is genuine guidance. It stops short of saying when to prefer another sibling (e.g. aggregation vs. rank) or what happens with ties or non-numeric input.

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