Skip to main content
Glama
dataparity

dataparity

dataparity_delete_diff_run

Permanently delete a saved diff report from local history using its run ID to remove outdated comparison records.

Instructions

Permanently delete a saved diff report from local history by run id.

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_delete_diff_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesSaved diff run id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.6/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 burden. It does disclose the most important trait, that deletion is permanent, which is genuinely useful. It says nothing about permissions, what happens when the run id does not exist, or whether any confirmation or soft-delete window exists.

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 with no filler, and the destructive qualifier 'Permanently' is front-loaded so an agent reads the risk first. Nothing is wasted, though the sentence could have carried one more useful clause at no cost.

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 single-parameter destructive tool with full schema coverage and no output schema, this is close to adequate: the identifier, the target, and the irreversibility are all stated. Only failure-mode and permission behavior are missing.

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 coverage is 100% with a single documented run_id, so the schema already does the work. The description's 'by run id' merely restates the parameter and adds no format, provenance, or validation detail beyond it.

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?

States a specific verb (delete) and resource (saved diff report) plus the scoping qualifier 'from local history' and the lookup key 'by run id'. That is enough to separate it from dataparity_delete_baseline and dataparity_get_diff_run without opening a schema, though it never explicitly names an alternative.

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?

The phrase 'permanently delete a saved diff report from local history by run id' implies the when (cleanup of a saved run) and the mechanism (run id), but offers no explicit when-not, no pointer to list_diff_runs for obtaining an id, and no guidance on retrying or on unknown ids.

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