Skip to main content
Glama

Compare rows side by side

dataset_compare

The rows of the Wärmepumpe Kosten Europa dataset whose column is any of the given values, in the order given, for "X vs Y" questions.

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>",
      "values": "<values>"
    },
    "name": "dataset_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
columnYes
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full disclosure burden. It does add real behavioral detail by promising rows come back 'in the order given', which is non-obvious and useful. It omits, however, what happens when a requested value matches nothing, whether matching is exact or case-sensitive, and whether the result is a raw row set or an actual comparison/diff.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, so there is no bloat to trim. But it is a grammatical fragment with awkward nested quoting, and the most decision-relevant information ('X vs Y' use case) is buried at the tail rather than front-loaded.

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?

For a two-parameter tool with no annotations and no output schema, the description should at minimum define matching semantics and the return shape. Instead it leaves the core question open — whether this performs a comparison or simply returns ordered matching rows — which is exactly the ambiguity the name 'compare' creates.

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 0%, so the description must compensate, and it partially does: 'column' is identified as the field to match on and 'values' as the set of accepted matches whose order matters. It says nothing about the schema's real constraints — at least 2 and at most 10 values, each a non-empty string — nor about matching semantics, leaving half the parameter meaning to guesswork.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the concrete dataset (Wärmepumpe Kosten Europa) and states that rows are selected where a column matches given values, which is more specific than the title 'Compare rows side by side'. But it is written as a noun phrase fragment with no verb, and it never clarifies what 'compare' actually means versus a plain filtered lookup, nor does it distinguish itself from siblings like dataset_row or dataset_search.

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?

'For "X vs Y" questions' is the only usage signal, and it is genuinely directional even if informal. There is no guidance on when NOT to use it and no named alternative (e.g., dataset_row for a single row, dataset_search for wider matching), so an agent must infer routing from sibling names alone.

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