Skip to main content
Glama
Sign In

site

by com.partnro
OverviewDiscussionsAdmin

Rank rows by a numeric column

dataset_top

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says the tool returns highest/lowest rows. It does not disclose ordering defaults, tie-breaking, handling of null/non-numeric values, limit behavior, output format, or any operational constraints.

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?

The description is a single compact sentence with an illustrative example phrase, containing no redundant filler. It is slightly awkward grammatically ('of the Partnro dataset by a numeric column') but remains concise and readable.

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?

The tool has no output schema and no annotations, and the description does not explain return format, the meaning of 'limit', or how the dataset name is used. An agent would need additional information to invoke the tool correctly beyond the basic ranking concept.

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% (only 'ascending' is explained). The description adds meaningful semantics for 'column' by specifying it must be numeric and clarifies 'ascending' via 'highest (or lowest)', but it leaves 'limit' completely unexplained despite the parameter being present.

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 title and description clearly state the operation: returning the highest (or lowest) rows of the Partnro dataset sorted by a numeric column. The example phrase 'which is the most/least X' makes the purpose concrete and distinguishes it from sibling tools like dataset_search or dataset_stats, though it does not explicitly name those alternatives.

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 description implies a usage context ('which is the most/least X') but does not state when to use this tool over dataset_compare or dataset_stats, nor does it mention any exclusions or prerequisites. Guidance is present only by implication, not explicit direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All site toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources