Skip to main content
Glama

Compare rows side by side

dataset_compare

The rows of the Sell My Business Quotes 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.4/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 does add one real behavioral fact — results follow the order of the supplied values — but says nothing about what is returned per match (single row? all matching rows?), whether the match is exact or case-sensitive, the 10-value cap, or how ties/duplicates behave.

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?

One short sentence with no padding, but it is front-loaded with an awkward possessive construction ("whose column is any of the given values") rather than leading with the action. Brevity here reflects under-specification rather than discipline.

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?

A two-required-parameter tool with no annotations and no output schema needs the description to explain the return shape and the comparison semantics. Neither is covered, and the "X vs Y" framing is left unexplained, so an agent cannot confidently predict what comes back.

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

Parameters2/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. It clarifies that "column" selects the comparison field and that "values" are the alternatives whose order determines result order, which is genuinely useful, but it never states that 2-10 distinct values are required, whether matching is exact, or how to handle repeated rows for a value.

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 sentence names the resource (rows of the Sell My Business Quotes dataset) and the filter (column matches any of the given values, order preserved), and it gestures at comparison use with "X vs Y" questions. But it is a noun-phrase fragment with no verb, and it never says what the tool actually does with those rows (return them? render them side by side?). An agent can guess the filtering behavior but not the output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

"for 'X vs Y' questions" is the only routing signal, and it is vague — it does not say when to prefer this over dataset_search, dataset_row, or dataset_top, nor any precondition or exclusion. No explicit when-not guidance is given.

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