Skip to main content
Glama

Compare rows side by side

dataset_compare

The rows of the Asbestos Survey Cost 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 are provided, so the description carries the full behavioral burden. It mentions that rows are returned 'in the order given', which is useful, but says nothing about read-only status, permissions, rate limits, error behavior when a column is missing, or the shape of the returned rows. For a tool with zero annotation coverage, this is a significant gap.

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?

The description is a single short fragment with no wasted words and is front-loaded with the resource. However, the fragment structure and ambiguous phrasing ('whose column is any of the given values') make it less clear than a well-formed sentence would be.

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 only two required parameters and no output schema, so the description should be complete enough for correct invocation. Instead, it leaves critical details unspecified: whether it returns a side-by-side comparison despite the title, what the output looks like, whether it is read-only, and what happens if the column or values are invalid.

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. It clarifies that 'column' refers to a dataset column and 'values' are matched against it, and that order is preserved. However, it omits constraints present in the schema (minItems 2, maxItems 10, minLength 1) and does not explain acceptable value formats or failure modes.

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 Asbestos Survey Cost dataset) and a filtering condition (column is any of the given values, in order), with a hint of use for 'X vs Y' questions. However, it is a sentence fragment that never states the operation (retrieve? compare? return?) and does not clearly explain how the tool differs from a simple filter 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' implies when to use the tool, giving a clear contextual hint. But there is no explicit guidance on when not to use it, no named alternatives among the many sibling dataset tools, and no prerequisites or exclusions.

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