Skip to main content
Glama

Permanently delete (irreversible)

permanent_delete_entity
DestructiveIdempotent

Permanently and IRREVERSIBLY hard-delete an entity from the recycle bin. The entity and all its children are removed from the database — this cannot be undone. Requires Admin role. Call once with no token to preview; re-call with the returned confirm_token and an idempotency_key to commit. entity_type must be one of: Customer, Project, Task, SubTask. Refused (CONFLICT.STATE_CONFLICT) when the entity is not in the recycle bin (reason NOT_IN_RECYCLE_BIN) or when anything under it is live - restored, or never deleted (reason LIVE_DESCENDANTS).

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": {
      "entity_id": "<entity_id>",
      "entity_type": "<entity_type>"
    },
    "name": "permanent_delete_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYesId of the recycle-bin entity to permanently delete.
entity_typeYesType of entity to permanently delete. One of: Customer, Project, Task, SubTask.
confirm_tokenNoToken returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
idempotency_keyNoRequired when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds substantial context the schema cannot convey: irreversibility, cascading removal of children, the Admin permission requirement, token expiry (~10 min), idempotent retry behavior, and exact error codes with their reasons. This is a mutation tool where knowing how to preview safely and why a commit might be rejected is exactly what an agent needs.

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?

Four sentences, front-loaded with the irreversible-destructive consequence, then preconditions, then protocol, then failure modes. Only waste is the entity_type value list, which duplicates the schema enum verbatim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description explains what the preview call returns (a confirm_token), how long it lasts, and the exact error shapes an agent must handle. For an irreversible 4-parameter mutation, nothing needed to call it correctly is missing.

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 coverage is 100%, so baseline is 3, but the description goes beyond per-field docs by explaining how confirm_token and idempotency_key work together as a preview-then-commit handshake. The entity_type enum is restated redundantly, but the protocol meaning attached to confirm_token adds real value.

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 first sentence gives a specific verb and resource with crucial qualifiers: "Permanently and IRREVERSIBLY hard-delete an entity from the recycle bin." The recycle-bin scope plus the cascade note ("The entity and all its children are removed") clearly separates this from restore_entity and the soft delete_* siblings.

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 states the two-phase protocol explicitly (call once with no token to preview, re-call with confirm_token and idempotency_key to commit) and spells out the conditions under which the call is refused (NOT_IN_RECYCLE_BIN, LIVE_DESCENDANTS). The Admin role prerequisite is called out. It stops short of naming an alternative tool for the case of a live entity, so it is not a full when/when-not/alternatives mapping.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources