Skip to main content
Glama
dataparity

dataparity

dataparity_get_diff_run

Retrieve a saved full table diff report using a run ID from a prior comparison or run listing, so you can review what changed and where changes concentrate.

Instructions

Retrieve a previously saved full diff report by the run id returned from dataparity_diff_tables or dataparity_list_diff_runs.

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": {
      "run_id": "<run_id>"
    },
    "name": "dataparity_get_diff_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesSaved diff run id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.8/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 convey that this is a retrieval of a persisted artifact ("previously saved"), implying a safe read. It says nothing about behavior on a missing or expired run id, retention of saved runs, or the size/shape of what comes back, which matters for a tool with no annotation coverage.

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?

One front-loaded sentence with the verb, resource, and input provenance in order of importance. No filler or redundant restatement of the schema.

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 simple single-parameter lookup this covers the essentials, but with no output schema and no annotations the description should say something about the returned report or failure on an unknown run id. As written, an agent knows how to call it but not what to expect back.

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 description coverage is 100% for the single run_id parameter, so the baseline would be 3. The description adds provenance the schema lacks: the id must come from dataparity_diff_tables or dataparity_list_diff_runs, which is actionable meaning beyond "Saved diff run id."

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 pairs an explicit verb ("Retrieve") with a specific resource ("a previously saved full diff report") and the key (run id), so an agent can immediately distinguish it from a list-style tool. It stops short of explicitly contrasting with dataparity_list_diff_runs, leaving the boundary to be inferred from the phrase "full diff report".

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 tells the agent exactly where the required run_id comes from (dataparity_diff_tables or dataparity_list_diff_runs), which is the main precondition for calling this tool. There is no explicit when-not guidance or note about invalid/expired run ids.

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