Skip to main content
Glama

site

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the FindAgency 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/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 disclosure burden. It reveals only the ranking semantics; it says nothing about the default limit (schema caps at 50 but gives no default), how ties are broken, what happens with a non-numeric or unknown column, or what shape the result takes. For a tool with zero annotation coverage, that leaves the agent guessing on several behaviors.

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 no filler; the selection semantics come first and the example phrasing follows. It is efficient, though slightly cryptic in its use of a quoted question rather than plain language.

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?

The tool is simple (3 params, flat object, no output schema), so expectations are modest. Still, an agent cannot know the default row count, tie-breaking, or error behavior for invalid columns, which are meaningful gaps for a ranking tool.

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 only 33%. Only 'ascending' carries a schema description, and the description itself adds nothing beyond restating direction ('highest (or lowest)'). The 'limit' parameter's default is undocumented in both places, and 'column' is only vaguely implied by 'by a numeric column'. The description does not compensate for the coverage gap.

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 specific resource: returning the highest or lowest rows of the FindAgency HQ dataset ranked by a numeric column. The parenthetical 'which is the most/least X' makes the intent unambiguous. It does not differentiate itself from siblings such as dataset_stats or dataset_search, which typically operate over aggregates or filters rather than top-N ranking.

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 example question ('which is the most/least X') implies the usage context of superlative lookups, which is useful framing. However, it never says when to prefer this over dataset_stats or dataset_search, nor any prerequisite such as the column needing to be numeric and available in dataset_columns.

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