Skip to main content
Glama

Outil.io

Delete invoice draft

delete_invoice_draft
Destructive

Supprimer un brouillon uniquement. Une pièce numérotée est conservée.

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": {
      "id": "<id>",
      "version": "<version>"
    },
    "name": "delete_invoice_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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, so the mutation profile is known. The description adds real value beyond that by disclosing the safety boundary: only drafts are affected and numbered documents survive untouched. It still omits whether the deletion is recoverable and what the caller gets back.

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?

Two short sentences with no padding, and the scoping restriction is front-loaded ahead of the preservation note. The only friction is that it is written in French while the schema, annotations, and title are English, and "pièce numérotée" is slightly oblique phrasing.

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

Completeness3/5

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

For a destructive two-parameter mutation with no output schema, the description covers the blast radius well but leaves parameter behavior and failure modes unaddressed. It is adequate to know when the tool applies, not fully adequate to know how to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two required parameters, id and version, and the description says nothing about either. In particular the meaning of "version" (presumably an optimistic-concurrency guard whose mismatch would fail the delete) is left entirely unexplained, so the description does not compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Supprimer un brouillon uniquement" states a specific verb (delete) and resource (draft), and the word "uniquement" scopes it away from non-draft invoices. It never uses the word "invoice" or "facture" itself, so the resource relies on the title and tool name to be unambiguous, but the intent is still recoverable.

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

Usage Guidelines3/5

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

"Uniquement" plus "Une pièce numérotée est conservée" gives an implicit when-not condition: issued/numbered documents cannot be removed with this tool. However, it names no alternative for those cases (e.g. an update or cancel path) and gives no preconditions, so guidance is implied rather than explicit.

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.