Skip to main content
Glama
dataparity

dataparity

dataparity_delete_baseline

Permanently delete a saved table baseline by name, removing obsolete comparison references and keeping stored baseline data current.

Instructions

Permanently delete a saved table baseline by name.

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

Input Schema

NameRequiredDescriptionDefault
nameYesSaved baseline name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose the single most important trait for a mutation tool, irreversibility ('Permanently'), which is genuine added context. It does not say what happens when the name is not found, whether dependent diff runs or comparisons are affected, or what permissions are required, leaving notable gaps for a destructive operation.

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 short sentence, front-loaded with the destructive verb and the permanence qualifier, with zero filler. It is efficient, though its brevity is partly the cause of the behavioral and usage gaps noted elsewhere.

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?

The tool is simple (one required parameter, no nesting, no output schema), and the schema fully documents the input, so the description is close to sufficient. However, for an irreversible delete with no annotations to fall back on, an agent still lacks error behavior, dependency effects, and permission expectations.

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% for the single parameter, and the schema already defines 'name' as the 'Saved baseline name'. The description's 'by name' only restates that the identifier is the lookup key, adding no format, case-sensitivity, or exact-match detail beyond the schema. Baseline 3 is appropriate.

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 uses a specific verb and resource ('Permanently delete a saved table baseline') plus a disambiguating qualifier ('by name'), so an agent can tell this apart from create_baseline, compare_baseline, and list_baselines. It stops short of explicitly naming a sibling it supersedes, which keeps it out of the top band.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites (does a baseline need to be unused, or does deletion require ownership?), and no routing to alternatives such as compare_baseline or list_baselines for verification before deletion. The only usage signal is the implied caution of the word 'Permanently'.

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