Skip to main content
Glama
dataparity

dataparity

dataparity_compare_baseline

Compare a configured table against a saved baseline to identify schema differences and changed hash buckets for the same source and table.

Instructions

Compare a configured table with a saved baseline for the same source and table. Returns schema differences and changed hash buckets; use dataparity_diff_tables for row-level details against a live table.

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": {
      "name": "<name>",
      "source": "<source>",
      "table": "<table>"
    },
    "name": "dataparity_compare_baseline"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSaved baseline name.
tableYesTable name, optionally schema-qualified.
sourceYesConfigured source name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the return content (schema differences and changed hash buckets), which compensates for the absent output schema, but says nothing about failure behavior when the baseline is missing, permissions required, or cost/expense of comparing large tables.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, with the primary purpose front-loaded before the sibling routing hint. Nothing is repeated from the schema or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read comparison with full schema coverage, the description covers purpose, return content, and the main alternative. The remaining gap is behavioral: no annotations means error/permission behavior and whether the comparison is a pure read still have to be inferred.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description adds real meaning by stating the baseline is looked up 'for the same source and table', implying the three parameters must be mutually consistent rather than independent lookups. That coordination constraint is not expressed in the schema field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Compare a configured table with a saved baseline') and constrains scope to the same source and table. It also names the sibling it is not (dataparity_diff_tables), so an agent can distinguish the two without reading either schema.

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?

Gives an explicit alternative and the condition that selects it: use dataparity_diff_tables for row-level details against a live table. Missing an explicit note that a baseline must already exist under the given name/source/table (see dataparity_create_baseline), but the usage context is otherwise clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.