Skip to main content
Glama
dataparity

dataparity

dataparity_create_baseline

Capture a named baseline of a configured table's schema and bucket-level canonical hashes, excluding row values, so later comparisons can detect data or schema drift.

Instructions

Capture a named baseline for a configured table. The local store keeps schema and bucket-level canonical hashes, not table row values. A later dataparity_compare_baseline checks for data or schema drift.

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>",
      "key_columns": "<key_columns>"
    },
    "name": "dataparity_create_baseline"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesUnique name for this baseline.
tableYesTable name, optionally schema-qualified.
sourceYesConfigured source name.
key_columnsYesColumns that identify rows and determine fingerprint buckets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.5/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 behavioral burden, and it does disclose something genuinely useful: what is persisted (schema and bucket-level canonical hashes, not row values). That tells the agent the operation is cheap/privacy-preserving. However, it says nothing about what happens on duplicate names, whether state is overwritten, required permissions, or whether the call is reversible.

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?

Three short sentences, front-loaded with the action, then the storage semantics, then the follow-up tool. No filler or repetition. Slightly dense phrasing in the middle sentence but every clause earns its place.

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 four-required-param creation tool with no annotations and no output schema, the description covers what it creates, where it is stored, and how it will be consumed. The main residual gap is return/identity information (what the agent gets back to reference this baseline later) and duplicate-name behavior.

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 100%, so all four parameters are already documented, and the description adds no parameter-level detail beyond what the schema states (including the bucket meaning of key_columns). Baseline 3 applies when the schema does the heavy lifting.

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?

"Capture a named baseline for a configured table" gives a specific verb and resource, and the closing sentence names dataparity_compare_baseline as the consumer, so an agent can tell it apart from the list/delete/compare siblings. It doesn't explicitly rule out the other baseline tools, but the creation framing is unambiguous.

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 description establishes a workflow relationship ("A later dataparity_compare_baseline checks for data or schema drift"), which implies this tool is called first to set up a comparison point. There are no explicit when-not conditions, no note on whether re-running with an existing name is allowed, and no preconditions such as needing the source already configured.

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