Skip to main content
Glama

MaxRechnung

Beleg löschen

delete_sales_document
Destructive

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

Beleg löschen

Löscht den Beleg endgültig; eine daraus entstandene Rechnung bleibt bestehen (Bezug darauf entfällt). Scope invoices:draft.

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_sales_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInterne `id` des Belegs (UUID), nicht die Belegnummer. Zu einer Nummer (z. B. `AN-2026-0004`) liefert `GET /sales-documents?number=…` (MCP: `list_sales_documents` mit `number`) die `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description reinforces that deletion is final and that a derived invoice persists without the reference – a genuine side effect beyond the annotations. It also discloses the billing tiers and the required 'invoices:draft' scope. It says nothing about confirmability, error behavior, or the response, so beyond annotations it adds moderate rather than rich context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short, but the body redundantly repeats the title as a standalone heading ('Beleg löschen') right after the tier line. The tier/plan sentence is contextual but not essential to invoking the tool correctly.

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 single-parameter destructive tool with annotations already flagging destructiveness, the description covers permanence, the surviving-invoice side effect, the required scope, and plan availability. Only return-value and failure behavior are unaddressed, which is acceptable without an output schema.

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% and the parameter itself documents that a UUID (not the document number) is wanted plus how to resolve a number via list_sales_documents. The description adds no further parameter meaning, so the baseline 3 applies.

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 states a specific verb and resource ('Löscht den Beleg endgültig') and adds a distinguishing nuance: an invoice derived from the document survives while its reference disappears. It never names a sibling tool to contrast with (e.g. cancel_invoice or delete_invoice_draft), so it stops short of full sibling-level differentiation.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. The permanence note and the 'invoices:draft' scope imply the operation is irreversible and requires that permission, but the agent is never told to prefer another tool when a document has already been invoiced or when only status change is intended.

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