Skip to main content
Glama

Rank rows by a numeric column

dataset_top

The highest (or lowest) rows of the Tachovo 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 supplied, so the description carries the full disclosure burden. It never states that this is a read-only operation, that the dataset is fixed to Tachovo, that at most 50 rows can come back, or what shape the returned rows take — behavior a caller must guess at.

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 that leads with the operation and resource. The trailing quoted gloss is slightly redundant with "highest (or lowest)" but is short and aids recall, so it mostly earns its place.

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 an undocumented `limit` parameter, the definition does not carry enough for confident invocation. An agent still needs to know whether this is safe to call, what the default row count is, and roughly what a returned row contains.

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%, so compensation is needed. The description does add real meaning for one parameter by constraining the column to a numeric one, and it covers the direction choice, but the `limit` parameter is left entirely undocumented in both schema and description, including its default.

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 concrete operation (return the highest or lowest rows) on a named resource (the Tachovo dataset) with the axis specified (a numeric column), plus a natural-language gloss of the use case. It is unambiguous on its own, but it does not say how it differs from siblings such as dataset_stats or dataset_row, which also surface data values.

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 framing "which is the most/least X" implies when the tool is appropriate, giving an agent a usable cue. However, there is no explicit condition for choosing it over dataset_stats or dataset_row, and no stated 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