Skip to main content
Glama

MaxRechnung

Entwurf löschen

delete_invoice_draft
Destructive

Tarif: in jedem Tarif (Free, Pro, Business).

Entwurf löschen

Löscht einen Entwurf endgültig und feuert invoice.deleted. Festgeschriebene Belege lehnen das mit 409 ab — die werden storniert (POST /invoices/{id}/cancellations). Scope invoices:draft (oder invoices:write).

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

Input Schema

NameRequiredDescriptionDefault
idYesInterne `id` der Rechnung (UUID), nicht die Belegnummer. Zu einer Nummer (z. B. `RE-2026-0004`) liefert `GET /invoices?number=…` (MCP: `list_invoices` mit `number`) die `id`.

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 declare destructiveHint=true, but the description adds what the annotations cannot: deletion is permanent, it emits an `invoice.deleted` event, it fails with 409 on finalized invoices, and it requires scope `invoices:draft` (or `invoices:write`). That is real behavioral context beyond the structured fields.

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?

Dense and front-loaded with the tier note and repetition of the title ('Entwurf löschen') taking the opening, though both are one line each. The remaining sentences are all load-bearing, covering effect, event, error case, alternative, and scope.

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 single-parameter destructive operation with no output schema, the description covers everything an agent needs: permanence, side effects, failure mode, prerequisite scope, and the correct alternative tool for non-draft invoices.

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 100% and the single `id` parameter already documents the UUID-vs-document-number distinction and the lookup route. The description adds nothing about the parameter, so the baseline 3 applies since the schema carries this burden entirely.

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 and resource ('Löscht einen Entwurf endgültig') and immediately clarifies the boundary: only drafts, since finalized invoices reject with 409. An agent can distinguish this from cancel_invoice or delete_sales_document from the text alone.

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?

Gives an explicit exclusion (Festgeschriebene Belege → 409) and the alternative path to use instead (POST /invoices/{id}/cancellations, i.e. the cancel_invoice sibling). It also states availability across all plans, so an agent knows there is no tier gating to check first.

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