Skip to main content
Glama

Compare rows side by side

dataset_compare

The rows of the Corp Tax Calculator 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.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and leaves most of it unaddressed. It does not confirm the operation is read-only, does not say what happens when a value matches no rows, and does not state the result ordering or size. 'In the order given' is the only behavioral hint and it is ambiguous about whether it applies to the values or the returned rows.

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 sentence with no filler, and the dataset scope is front-loaded. Its problem is under-specification rather than verbosity, so the tight length is not itself a flaw.

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 query tool with no annotations and no output schema, the agent needs to know the return shape, ordering, and no-match behavior. None of that is present, and the fragmentary grammar makes the matching semantics ('any of the given values') the only thing clearly conveyed.

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%, and the description is the only source of meaning for both parameters: 'column' is the field to match on and 'values' is a set of accepted values. That is genuine added meaning, but it omits the 2-to-10 value constraint and the column-name format, both of which live only in an undescribed schema.

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 Corp Tax Calculator dataset) and a filter condition (column matches any of the given values, in the given order), so the operation is inferable. But it is a noun phrase with no verb ('Returns...'), and it never distinguishes itself from siblings like dataset_row or dataset_search, which an agent must choose between.

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 trailing clause 'for "X vs Y" questions' gives one concrete usage context, which implies when to reach for this tool. It stops there: no exclusions, no named alternative for single-row lookups, and no guidance on how many values constitute a sensible comparison.

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