Skip to main content
Glama

delete_diagram

DestructiveIdempotent

Permanently delete a database diagram by its UUID. This cannot be undone, so confirm with the user before proceeding.

Instructions

Permanently delete a diagram. This cannot be undone — confirm with the user before calling it.

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": {
      "diagram_id": "<diagram_id>"
    },
    "name": "delete_diagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
diagram_idYesThe diagram id (a UUID), from list_diagrams.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds real value beyond them by emphasizing irreversibility ('This cannot be undone') and imposing a user-confirmation step, though it says nothing about permissions or what is returned after deletion.

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?

Two sentences, no filler, with the destructive nature and the confirmation requirement front-loaded before any call is attempted.

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 annotation coverage and no output schema, permanence plus the confirmation instruction covers what an agent needs. Only the post-deletion response behavior is left unstated, which is a minor gap.

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% and diagram_id is documented in the schema as a UUID sourced from list_diagrams. The description adds no further meaning about the parameter, so the baseline 3 applies.

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?

States a specific verb ('Permanently delete') and resource ('a diagram'), and the word 'permanently' immediately distinguishes it from any recoverable/soft-delete or update operation. An agent can tell this apart from create_diagram, get_diagram, and update_diagram without inspecting schemas.

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?

Gives a clear precondition for calling: confirm with the user first. There is no competing deletion sibling to route away from, so no exclusions are needed, but it stops short of spelling out when deletion is appropriate versus e.g. update_diagram.

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