Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the HardscapeDesk 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 behavioral burden and adds little: it does not state that the operation is read-only, what happens with ties, nulls, or non-numeric columns, what the default row count is, or what shape the result takes. Only the direction semantics are conveyed, which the schema already covers.

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 the key scoping phrase front-loaded; nothing is padded. The trailing quoted example is slightly informal but earns its place by illustrating the intended question shape.

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 should explain what a 'top' result contains and how many rows come back by default. Neither is addressed, and the undefined 'limit' behavior is a real gap for an agent trying to size its request.

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?

With only 33% schema description coverage, the description must compensate. It does add real meaning by restricting 'column' to a numeric column, which the schema does not enforce, and it clarifies the ascending/descending intent. It says nothing about the 'limit' parameter, its maximum of 50, or any default, leaving a full third of the parameters undocumented 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 specific operation on a specific resource: ranking rows of the HardscapeDesk dataset by a numeric column, in either direction. It implicitly distinguishes itself from dataset_row (single row) and dataset_stats (aggregates), though it never names those siblings 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 quoted intent phrase "which is the most/least X" gives a usable mental model for when to reach for this tool, and "highest (or lowest)" signals the direction choice. However, there is no explicit when-not guidance and no pointer to alternatives such as dataset_stats when the agent actually wants aggregate extremes rather than the winning rows.

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