Skip to main content
Glama

Compare rows side by side

dataset_compare

The rows of the FlatRateBook 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 supplied, so the description carries the full disclosure burden. It never states that this is a read-only lookup, what volume of rows comes back, whether the value list caps results, or what the returned rows look like; only the ordering behavior ("in the order given") is disclosed.

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?

It is a single short line with no filler, and the filter scope is front-loaded. However the sentence is grammatically incomplete (a noun phrase rather than a statement of what the tool does) and the nested quoting is hard to parse, which costs readability.

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?

With no annotations, no output schema, and 0% parameter documentation, the description should explain read-only safety, result shape, and the 2-10 value constraint's effect. It covers only the ordering behavior and the comparison-question use case, leaving an agent unable to predict the response.

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 explain both parameters. It does add real meaning for `values` by declaring that output row order follows the given value order, which the schema does not say, but it only says "column" without indicating whether that is a column name from dataset_columns or what happens for an unknown column.

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 ("The rows of the FlatRateBook dataset") and a filter condition ("column is any of the given values"), which is enough to infer a filtered row-fetch. But it is a sentence fragment with no verb, and it does not distinguish itself from siblings like dataset_row or dataset_search that could also return matching rows.

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?

"for 'X vs Y' questions" gives a clear usage context and is the strongest part of the definition. It offers no explicit when-not guidance and does not name an alternative for non-comparison lookups, so the agent must infer the boundary from siblings' names.

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