Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the PotterySuppliesHQ 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 supplied, so the description must carry the behavioral load. It implicitly establishes a read-only ranking operation and adds the constraint that the ranking column must be numeric, but it never states the default row count, the cap of 50, tie-handling, or what happens if the column is non-numeric or missing.

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 core operation and followed by an illustrative question pattern. The colon-and-quote construction is slightly clunky but wastes no words and adds a concrete use case.

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 annotations, no output schema, and a three-parameter input, the description should say more about what is returned (which columns, how many rows by default) and how errors behave. It covers the core semantics adequately for a simple read tool but leaves meaningful gaps.

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%: only `ascending` is documented in the schema, while `column` and `limit` have no schema descriptions. The description partially compensates by requiring `column` to be numeric, but says nothing about `limit` (its default, or that it is capped at 50), leaving one parameter effectively unexplained 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?

States a specific operation (return the highest or lowest rows ranked by a numeric column) on a specific resource (the PotterySuppliesHQ dataset), which is clearly distinct from siblings like dataset_stats or dataset_row. It stops short of naming a sibling to contrast with, so the differentiation is inferential rather than explicit.

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 pattern "which is the most/least X" gives an implicit trigger condition, which is a useful hint about the question shape this tool answers. There is no guidance on when not to use it, no named alternatives (e.g. use dataset_stats for aggregates), and no note on prerequisites such as the column being numeric beyond the phrase 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