Skip to main content
Glama

Compare rows side by side

dataset_compare

The rows of the Tide Times Compare 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.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses that rows are filtered by column values and returned in the order given, which is useful behavioral context. However, it omits whether the operation is read-only, any limits, pagination, or error behavior.

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 compact sentence with no filler. It is front-loaded with the returned rows and filter condition, though the sentence-fragment style is slightly awkward.

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 read/filter tool with no annotations and no output schema, the description covers the core selection logic and use case. It still leaves important gaps around matching semantics, return size, and pagination, so it is only partially complete.

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 coverage is 0%, so the description must compensate. It clarifies that 'column' is the field to match and 'values' are alternatives, and that result order follows the value order. It does not specify exact vs partial matching, case sensitivity, or duplicate handling.

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 identifies the resource (rows of the Tide Times Compare dataset) and the filter logic (column matches any of the given values), and signals the 'X vs Y' use case. It lacks an explicit verb, but the retrieval semantics are inferable and differentiated from a generic search.

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?

It names a specific use case ('X vs Y' questions) but does not say when to prefer a sibling such as dataset_search or dataset_row, nor when this tool is inappropriate. Guidance is implied rather than explicit.

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