Skip to main content
Glama

Rank rows by a numeric column

dataset_top

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

With no annotations, the description carries the full behavioral burden, and it discloses very little: it does not confirm this is a read-only query, does not say how ties or nulls in the ranking column are handled, and does not state the default row count when limit is omitted. Only the ranking direction (high vs low) is conveyed, and that is already in the schema.

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 front-loaded sentence with the core operation first and the colloquial use case second; no filler. The trailing quoted example is slightly informal but earns its place as a usage cue.

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 tool with no annotations, no output schema, and two of three parameters undocumented, the description should do more: it never says whether full rows or just column values are returned, nor what happens by default on limit. An agent could call it, but would be guessing at the result shape.

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 33% — only ascending is documented — so the description partially compensates by constraining column to a numeric column, which is meaningful added semantics. It says nothing about limit (range, default, or that it caps output size), leaving that parameter undocumented 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 Curtilo dataset by a numeric column" states a specific operation, resource, and ordering axis, so an agent can tell this is a top-N ranking tool rather than a filter or aggregate. It does not name any sibling (e.g. dataset_stats or dataset_search) to sharpen the boundary, so it falls short of a 5.

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 "which is the most/least X" framing gives an implied use case for ranking questions, which is genuine guidance. However, there is no statement of when NOT to use it, no pointer to an alternative for filtered or paginated retrieval, and no prerequisite or precondition noted.

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