Skip to main content
Glama

Compare rows side by side

dataset_compare

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

B3.2/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 behavioral burden. It does disclose that results are returned 'in the order given' and that the column may match 'any of the given values,' but it omits read-only status, authentication requirements, rate limits, matching rules, and return shape.

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 sentence with no wasted wording, and the core filtering and ordering semantics are front-loaded. Its fragment structure and nested quotation marks make it slightly less readable than a direct action statement.

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 output schema or annotations, the description covers the dataset, filter, ordering, and use case. However, it leaves out the exact return structure and matching behavior, which are important for an agent to invoke it correctly.

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 adds useful meaning by saying the column is matched against 'any of the given values' and that result order follows the supplied order, but it does not clarify exact matching, case sensitivity, or how the column name is interpreted.

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 clearly identifies the resource as rows of the Tachovo dataset and the filter as a column matching any of the given values. It also gives the ordering behavior and the 'X vs Y' use case, though it is phrased as a noun fragment and does not explicitly distinguish itself 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' gives an implied usage context, but there is no explicit when-to-use versus when-not-to-use guidance. No sibling alternatives are named, so an agent must infer that this tool is for comparison-oriented row retrieval rather than generic search or single-row lookup.

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