Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Coshhvo 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. It implies a read of ranked rows but says nothing about tie handling, what happens with a non-numeric column, the default row count, or the shape of the returned rows — all significant for a 3-parameter tool with zero annotation coverage.

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 stated first and the extremal-question framing appended as illustration. No filler, though the quoted example is slightly informal and substitutes for more concrete usage guidance.

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?

With no annotations, no output schema, and one of three parameters documented only in the schema, the description should do more work. It leaves the row-count semantics, tie-breaking, error behavior on non-numeric columns, and return shape entirely unaddressed.

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 only 33% — only 'ascending' is documented in the schema, so the described fields fall on the description. It adds genuinely useful meaning by requiring the column be numeric and by mapping 'highest/lowest' to the sort direction, but 'limit' is never mentioned, leaving the 1-50 cap and default count unexplained.

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 names a specific operation on a specific resource: returning the highest or lowest rows of the Coshhvo dataset ranked by a numeric column. The quoted 'which is the most/least X' frames the intent clearly, which distinguishes it from siblings like dataset_stats or dataset_search, 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?

The 'most/least X' example implies when this tool fits (extremal-value questions), but there is no explicit statement of when to prefer it over dataset_stats, dataset_search, or dataset_compare, and no exclusions or prerequisites.

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