Skip to main content
Glama
Sign In

OrgGen AI

by ai.orggen
OverviewDiscussionsAdmin

delete_entity

Destructive

Deletes an ERD entity AND every NESTED entity below it (parentId, at any depth), as well as everything that references any of them: fields, relations, lineage, assignments, dependencies, data sources. The deletion is PERMANENT: no trash and no undo by the tool (only a version saved before the call, via restore_version — which replaces the WHOLE schema —, gets back what was deleted). It takes away what is listed here and what depends on the block (its content, its sharing grants, its block links); the attached comments, tasks and documents are not destroyed (they survive, detached). This is NOT an erasure of personal data: that goes through deleting the account or the project. If comment threads were anchored on the deleted entities, they SURVIVE (they are not destroyed) but become invisible on the canvas: reported via orphanedComments + note. Same for the attached TASKS (create_tasks): they survive, move to 'No subject' and re-attach automatically if a block with the same id is recreated — reported via detachedTasks + note.

Input Schema

NameRequiredDescriptionDefault
idYesID of the entity to delete (cascades to the nested entities + fields, relations, lineage, assignments, dependencies, dataSources)
expectedProjectIdNoUUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / expectedProjectId / description
      Previous value: -"UUID du projet visé par CET appel. Cible RÉELLEMENT ce projet au lieu du projet de session. Refusé sans rien modifier si l'accès n'est pas accordé."New value: +"UUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted."
    • changedInput schema / properties / id / description
      Previous value: -"ID de l'entité à supprimer (cascade sur les entités imbriquées + fields, relations, lineage, assignments, dependencies, dataSources)"New value: +"ID of the entity to delete (cascades to the nested entities + fields, relations, lineage, assignments, dependencies, dataSources)"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only supply destructiveHint=true; the description carries far more: cascade at any depth, PERMANENT with no trash/undo, the restore_version caveat (replaces the WHOLE schema), which attached artifacts survive detached (comments, tasks, documents), and the orphanedComments/detachedTasks/note reporting. It is consistent with the destructive annotation, adding substantial context the structured fields do not.

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?

Front-loaded correctly: deletion scope and permanence come first, survival semantics after. It is efficient but somewhat long and repetitive (comments and tasks each explained twice), which keeps it from a 5.

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?

For a destructive mutation with no output schema, the description is complete: it covers cascade behavior, irreversibility, recovery, what survives, and even the return fields (orphanedComments, detachedTasks, note). An agent has everything needed to call it correctly and warn the user.

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 the baseline is 3, but the description meaningfully enriches the `id` parameter by spelling out the cascade depth (parentId, any depth) and the full set of dependent artifacts removed. It adds little for `expectedProjectId`, which the schema already documents well.

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 (Deletes) and precisely scoped resource: an ERD entity plus every nested entity at any depth, plus all referencing artifacts (fields, relations, lineage, assignments, dependencies, data sources). The 'ERD entity / NESTED entity' framing implicitly separates it from sibling delete_cell, delete_field, delete_relation, so an agent can identify it without opening the schema.

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?

Provides a clear when-not and alternative: it is 'NOT an erasure of personal data: that goes through deleting the account or the project,' and names restore_version as the recovery path. However it gives no positive guidance on when to prefer this over other delete_* siblings, so it stops short of a full when/when-not/alternatives statement.

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

All OrgGen AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources