Skip to main content
Glama

site

Compare rows side by side

dataset_compare

The rows of the DoorsetBook 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

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the core selection behavior and the significance of value ordering, but it does not clarify exact-match semantics, case sensitivity, return shape beyond "rows," or limits such as the maximum number of values.

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 definition is a single compact sentence fragment with little wasted wording. It is concise, though the fragment structure and phrasing "column is any of the given values" are slightly awkward and not fully front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter retrieval tool with no annotations, no output schema, and no schema descriptions, the description covers purpose and basic parameter meaning. However, it leaves gaps around exact matching, return format, and how ordering applies to the returned rows.

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 explain both parameters. It meaningfully indicates that "column" selects the field to compare and "values" are alternatives to match in order, but it omits constraints such as minimum two values and maximum ten values.

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 description specifies the resource (rows of the DoorsetBook dataset) and the filtering operation (column value is any of the supplied values, preserving the given order). It is clear enough to distinguish a filtered row-retrieval operation, but it does not explicitly differentiate this from sibling tools such as 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "for 'X vs Y' questions" gives a clear intended use case for the tool. It does not explain when not to use it or name alternative sibling tools, but the context is explicit enough to guide selection for comparison-style queries.

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