Skip to main content
Glama

Compare rows side by side

dataset_compare

The rows of the Roofing Quotes UK 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.7/5.0
Behavior2/5

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

No annotations and no output schema, so the description carries the full burden. It does disclose one real behavioral trait – results follow the order of the supplied values – but says nothing about whether one row per value is returned, how multiple matches per value are handled, limits on result size, or what the comparison output looks like.

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 sentence with no filler, which is good, but the structure is a sentence fragment and the trailing clause 'in the order given' dangles ambiguously between the filter and the result ordering. Brevity here comes at the cost of parseability.

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 comparison tool with no annotations, no output schema, and zero documented parameters, the definition leaves too much unresolved: the shape of returned rows, whether rows are paired per value, and any result limits are all unstated. An agent could invoke it but could not predict its output.

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 for both parameters. It does convey the core relationship (a column name plus a set of values matched against it, with order significant), but omits the schema constraints (2–10 values) and does not say the column must be one of the dataset's actual column names.

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 identifies the resource (rows of the Roofing Quotes UK dataset) and a filter condition (column matches any of the given values, in the given order), which is more than a restatement of the title. However, it never states a verb, never explains the 'side by side' comparison promised by the title, and gives no way to distinguish it from siblings like dataset_search or dataset_row.

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 phrase 'for "X vs Y" questions' is a genuine usage hint that implies the intended scenario. There is no when-not guidance, no prerequisites, and no named alternative for plain single-value lookups, so the guidance stays at the implied level.

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