Skip to main content
Glama

Entwurf verwerfen

discard_draft
DestructiveIdempotent

Drop a previewed draft (invoice or offer) the user no longer wants, including the Entwurf at facturo.at. Only after the user said so. A draft already turned into a document cannot be discarded; deleting invoices and offers happens in the facturo web app.

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": {
      "draft_id": "<draft_id>"
    },
    "name": "discard_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 covered. The description adds genuinely new behavior: the deletion also removes the Entwurf on the remote facturo.at side, and it requires prior user confirmation. It stops short of saying whether the discard is recoverable or what a failed discard looks like.

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?

Three short sentences, front-loaded with the action, then the precondition, then the exclusion — no filler. The phrase 'including the Entwurf at facturo.at' is slightly opaque to a non-German reader but does carry real scope information.

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 one-parameter destructive tool with no output schema, the definition covers the confirmation requirement, the remote side effect, and the boundary against finalized documents. Remaining gaps are recovery/failure behavior and the source of draft_id, which are minor but not trivial for an irreversible operation.

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 0% for the single draft_id parameter, so the description must carry the meaning. Saying the draft is 'previewed' hints that the id comes from a preview call, but it never states the id format or how to obtain one, leaving a real gap for a destructive tool.

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?

The description opens with a specific verb and resource: drop a previewed draft (invoice or offer), and clarifies the scope extends to the Entwurf at facturo.at. It distinguishes this from finalizing, since a draft already turned into a document cannot be discarded, but it never names the sibling tools (preview_invoice, preview_offer, finalize_invoice) that produce or consume drafts.

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?

It states an explicit precondition ('Only after the user said so'), an explicit exclusion ('a draft already turned into a document cannot be discarded'), and routes the out-of-scope case (deleting real invoices/offers) to the facturo web app. An agent knows both when to call this and when to refuse.

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