Skip to main content
Glama

Compare rows side by side

dataset_compare

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

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full load and does disclose two real behaviors: matching is by value membership on a single column, and output order follows the input order. It does not say what happens when a value matches no row (omit, error, or placeholder), whether multiple rows per value can be returned, or that the result is bounded by the 10-value cap.

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?

One sentence, no filler, and the distinguishing detail (ordered output for comparison questions) is placed where it is seen immediately. The opening noun-phrase construction is slightly awkward to parse but costs no words.

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 lookup with no annotations and no output schema, the description covers selection and ordering semantics, which is the core. It leaves open the no-match and multi-match behavior and the cap on values, gaps an agent would likely hit on real 'X vs Y' calls.

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 has to explain both parameters. It does convey that 'column' is the match key and 'values' is a membership set whose order governs output, which is more than the bare schema types provide, but it adds no detail on matching rules (case sensitivity, exactness) or the minimum of 2 / maximum of 10 values.

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 names the resource (rows of the Dispatchzo dataset), the selection key (column matched against given values), and the output ordering ('in the order given'), and frames the tool around 'X vs Y' comparisons, which separates it from the search/top/stats siblings. It is a noun phrase rather than a verb-led statement, but the operation and scope are still unambiguous.

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

Usage Guidelines4/5

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

It gives a clear trigger condition: use this for 'X vs Y' questions, i.e. when specific named values must be pulled back and lined up. It does not state exclusions or name alternatives such as dataset_search for fuzzy lookup, so it stops short of a 5.

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