Skip to main content
Glama

Rank rows by a numeric column

dataset_top

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

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

With zero annotations, the description carries the full burden and only implies a read by describing the output as "rows of the dataset." It does not state the default limit, the hard cap of 50, tie-breaking behavior, what happens if the column is non-numeric, or the shape of returned rows.

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 with no filler; the ranking concept leads and the intent example follows. The trailing quoted example is slightly informal but earns its place by clarifying the question shape.

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, no-annotation, no-output-schema tool, the description conveys the core idea but leaves gaps an agent would want filled: default result count, return format, and error behavior on an invalid column. Adequate, not complete.

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 should compensate more. It does add meaning for `column` (must be numeric) and mirrors the highest/lowest direction that `ascending` controls, but it says nothing about `limit` or its 1-50 bounds, and never names the parameters directly.

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 the operation (returning highest/lowest rows), the resource (rows of the MultiplesBook dataset), and the dimension it ranks on (a numeric column). That is enough to separate it from dataset_row (single row) and dataset_stats (aggregates), though it never explicitly contrasts with any sibling.

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" is a useful trigger for when to reach for this tool, so usage is implied rather than stated. There is no guidance on when to prefer dataset_stats, dataset_search, or dataset_compare instead, and no 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