Skip to main content
Glama
Sign In

OrgGen AI

by ai.orggen
OverviewDiscussionsAdmin

delete_document

Destructive

Deletes a document PERMANENTLY — and its file attachment where applicable. Irreversible: a plain removal from the view without loss is done with update_document({archived: true}).

Input Schema

NameRequiredDescriptionDefault
documentIdYesIdentifier of the document to delete PERMANENTLY (and its file attachment where applicable). A plain removal from the view is done with update_document({archived: true}).
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 / documentId / description
      Previous value: -"Identifiant du document à supprimer DÉFINITIVEMENT (et sa pièce jointe le cas échéant). Un simple retrait de la vue se fait par update_document({archived: true})."New value: +"Identifier of the document to delete PERMANENTLY (and its file attachment where applicable). A plain removal from the view is done with update_document({archived: true})."
    • 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."
  2. Changed1 schema field changed
    • changedInput schema / properties / documentId / description
      Previous value: -"Identifiant du document à supprimer DÉFINITIVEMENT (et sa pièce jointe le cas échéant). Pour un simple retrait de la vue, préfère update_document({archived: true})."New value: +"Identifiant du document à supprimer DÉFINITIVEMENT (et sa pièce jointe le cas échéant). Un simple retrait de la vue se fait par update_document({archived: true})."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds valuable detail beyond that: the deletion is permanent, irreversible, and also removes the file attachment where applicable. It does not cover permission/authorization behavior, though the schema does partially address access refusal for expectedProjectId.

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 short sentences, front-loaded with the permanent-deletion warning and followed by the alternative. Every clause earns its place.

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?

A simple two-parameter destructive tool with no output schema and full schema description coverage. The description supplies the essential irreversibility and attachment-removal context, and annotations cover the destructive profile.

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%, so both parameters are already documented in the input schema. The description does not add syntax, format, or side-effect information beyond what the schema provides for documentId and expectedProjectId.

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 resource (document) and immediately distinguishes the operation from the softer alternative update_document({archived: true}). The 'PERMANENTLY' qualifier makes the destructive scope unambiguous.

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

Usage Guidelines5/5

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

Explicitly says this is irreversible and names the alternative tool and parameter for non-destructive removal, giving a clear when-not-to-use condition. No inference is required to choose between the two siblings.

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