Skip to main content
Glama

Compare rows side by side

dataset_compare

The rows of the PotterySuppliesHQ 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.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It reveals that matching is any-of and output order follows the supplied values, but it does not explain return shape (full rows vs comparison layout), read-only safety, missing-value behavior, or limits beyond the schema.

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?

It is a single front-loaded sentence with no filler, and the 'X vs Y' qualifier is useful. The phrasing is slightly awkward because it reads as a noun phrase rather than an action statement, but it is appropriately sized.

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?

With no annotations and no output schema, the definition should say more about what a caller receives and how the 'side by side' comparison is represented. It establishes the filtering/order contract but leaves return fields, row count, and edge cases unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must define both parameters. It explains that 'column' is the field to match and 'values' is an any-of list whose order controls result order, adding real semantics beyond the bare string/array schema; it still omits the 2-10 cardinality constraints, though those are in the schema.

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 states the returned resource (rows of the PotterySuppliesHQ dataset) and the filter/order semantics, and gives a use case ('X vs Y' questions). It is clear enough to distinguish from a single-row getter, though it never names an alternative sibling or explicitly resolves the 'compare' vs 'filter rows' ambiguity.

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?

It gives a concrete use case: 'X vs Y' questions, implying when to choose it. It does not state when not to use it or name a sibling alternative such as dataset_search, so it stops short of full routing guidance.

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