Skip to main content
Glama

Rank rows by a numeric column

dataset_top

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

C2.9/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 only the sort-direction concept. It does not state that this is a read-only operation, what the default limit is, how ties or null values are handled, or what the returned rows look like. That leaves an agent guessing on several traits that matter before calling.

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?

One front-loaded sentence with no filler, and the core ranking behavior leads. The stray internal quotation marks are a minor stylistic blemish rather than a comprehension problem; the issue with this description is thinness, not verbosity.

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, no output schema, and only 33% schema description coverage, the description is too sparse. An agent still lacks default limit behavior, tie-breaking, and any indication of the response shape, all of which the description would need to supply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low at 33%, so the description needs to compensate, and it partially does by implying the column must be numeric, which the schema's bare string type does not convey. It says nothing about limit (range 1-50, default unclear) or about the ascending parameter's default, so most parameter meaning is left undocumented.

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 on a named resource: it returns the highest or lowest rows of the Shortcodo dataset ranked by a numeric column. The 'most/least X' framing makes the intent concrete and distinguishable from sibling lookups like dataset_row or dataset_search, though it does not explicitly name a 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 'which is the most/least X' phrasing implies the use case well enough to route an agent here for ranking questions. However, there is no explicit when-not guidance, no mention of dataset_stats or dataset_compare as alternatives, and no prerequisites such as the column needing to be numeric (that is only obliquely implied).

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