Skip to main content
Glama

Compare rows side by side

dataset_compare

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

With no annotations, the description carries the full burden of behavioral disclosure. It does add one real trait — result rows come back 'in the order given' — but says nothing about match semantics (exact vs partial, case sensitivity), row limits, what happens when a value matches nothing, or whether this is a read-only operation.

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?

A single short sentence with no padding, but it is a sentence fragment missing a subject, so the core action is never stated. The important detail (order preservation, X-vs-Y usage) is present without being front-loaded.

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 two-parameter read tool with no output schema and no annotations, the description covers the filter concept but not the return shape (which columns come back per row), empty-result behavior, or the value count ceiling. It is minimally sufficient to attempt a call but not to predict its results.

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 explain both parameters. It clarifies that 'column' selects the filter field and that 'values' are matched against it with ordering preserved, but omits match type, case handling, and the 2–10 value bounds, leaving the agent to infer matching behavior from the schema alone.

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 definition describes the resource and filter semantics ('rows of the Kbasevo dataset whose column is any of the given values') but is a noun phrase with no verb, and never states whether it fetches, copies, or returns them. It hints at a distinguishing use case ('X vs Y' questions) but does not set itself apart from siblings like dataset_row or dataset_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?

The trailing clause 'for "X vs Y" questions' is a genuine intent cue and is the only routing signal present. There is no statement of when not to use it, no named alternative (e.g., dataset_search for free-text matching), and no prerequisites such as the column needing to exist.

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