Skip to main content
Glama

Rank rows by a numeric column

dataset_top

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

No annotations are supplied, so the description carries the full behavioral burden. It never states that this is a read-only, side-effect-free operation, does not mention the hard 50-row ceiling on results, and says nothing about tie-breaking or non-numeric column behavior. Only the ordering semantics (highest by default, lowest optionally) are disclosed.

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 compact sentence with the key ordering qualifier front-loaded; no filler. The trailing quoted example is slightly redundant but serves as a useful intent anchor.

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 tool with no annotations and no output schema, the description covers the core ranking behavior adequately but omits the result cap, the read-only nature, and the shape of returned rows. An agent could call it correctly but would learn important limits only from the schema or by trial.

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 description coverage is only 33%, with just `ascending` documented, so the description must compensate. It does add the important constraint that `column` must be numeric (the schema only says non-empty string) and restates the ascending/descending meaning for `ascending`, but it leaves `limit` and its 1-50 range entirely undefined.

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 concrete operation (return the highest or lowest rows) on a named resource (HomeCover HQ dataset) qualified by a numeric column. The 'which is the most/least X' gloss makes the intent immediately recognizable and clearly separates it from row-fetch or aggregate siblings, though no sibling is named 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?

Usage is implied through the natural-language question pattern 'which is the most/least X', which tells an agent what kind of question this tool answers. There is no explicit when-not guidance, no mention of the maximum limit cap, and no pointer to dataset_stats or dataset_search when ranking is not what's wanted.

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