Skip to main content
Glama

Compare rows side by side

dataset_compare

The rows of the Medcontra 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.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one genuine trait beyond the schema: results follow the order of the supplied values rather than dataset order. It says nothing about whether the tool is read-only (implied by the noun-phrase framing), what happens when a value matches no rows, or whether multiple rows per value are returned.

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 sentence with no wasted words, and the filter condition precedes the use-case hint, which is reasonable front-loading. The fragmentary grammar and the trailing "for 'X vs Y' questions" clause make it read as a doc snippet rather than a self-contained instruction.

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 zero schema description coverage on two required parameters, the description is the only source of behavioral information and it is one sentence. It omits return shape (full rows vs. selected columns), missing-value handling, and the meaning of the ordering guarantee — all things an agent needs before calling it for a comparison task.

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 must compensate, and it partially does: 'column' is identified as the field to match and 'values' as the match set, with the ordering constraint called out. It still leaves ambiguity about whether 'in the order given' refers to row ordering within each value or grouping of value blocks, and it never addresses the 2–10 item limit or missing-value behavior.

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 (rows of the Medcontra dataset) and the filter (column matches any of the given values), which is more specific than restating the name. However, it is a sentence fragment with no verb and no differentiation from siblings like dataset_search or dataset_row, so an agent cannot tell from the text alone why it should prefer this tool for retrieval.

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 concrete use case that implies when to reach for this tool, which is more than nothing. But there are no exclusions, no mention of when dataset_search or dataset_row would be the better choice, and no prerequisites stated.

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