Skip to main content
Glama
Sign In
DPF

DPF

by dpf-admin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Delete a data spec

delete_data_spec
DestructiveIdempotent

Permanently delete a data spec and its associated configuration. Specify the spec name and workspace to remove it from your DPF data workflows.

Instructions

Permanently delete a data spec and its associated configuration.

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": {
      "specName": "<specName>"
    },
    "name": "delete_data_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
specNameYesName of the data spec to delete.
workspaceIdNoWorkspace to act on. Defaults to your only workspace if you have exactly one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

While annotations already indicate destructive and idempotent behavior, the description adds 'permanently' and explicitly mentions that associated configuration is also deleted, which goes slightly beyond the annotations. However, it does not describe side effects like Cascading deletes or error conditions.

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?

The description is a single, succinct sentence that conveys the essential information without any redundant wording or unnecessary details.

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 simple delete operation, the description is sufficient, especially given the schema and annotations. It mentions the deletion of both the spec and its configuration, which covers the primary context. A minor omission is lack of mention of whether the operation is recoverable, but 'permanently' already implies that.

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?

The schema already provides descriptions for each parameter (specName and workspaceId) with 100% coverage. The tool description does not add further detail beyond the schema, so it meets the baseline but does not enhance understanding.

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?

The description clearly states the action (delete), the target resource (data spec and associated configuration), and adds 'permanently' to emphasize irreversibility. It is specific and easily distinguishes from other tools.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any cautionary notes about the destructive nature beyond the verb itself. It does not clarify scenarios where deletion should be avoided or prerequisites.

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

Deploy Server

Other Tools