Skip to main content
Glama

MaxRechnung

Beleg umwandeln

convert_sales_document

Tarif: ab Pro (darunter antwortet die API mit plan_required).

Beleg umwandeln

Erzeugt den Folgebeleg: order_confirmation oder delivery_note (neuer Beleg in derselben Kette, Antwort SalesDocument) oder invoice (Rechnungsentwurf mit nächster RE-Nummer, Zahlungsziel aus dem Profil, Antwort Invoice, feuert invoice.created). Angebot → AB/Lieferschein/Rechnung, AB → Lieferschein/Rechnung, Lieferschein → Rechnung. Ab Pro: Angebot → Rechnung; jedes Weiterführen in eine oder aus einer Auftragsbestätigung bzw. einem Lieferschein ab Business (403 plan_required). Der Ausgangsbeleg rückt im Status weiter; der Rechnungsentwurf zählt ins Monatskontingent. Steht der Beleg unter § 19 UStG (Kleinunternehmer), die Rechnungsvorgaben des Kontos inzwischen auf Umsatzsteuer, weist die Rechnung Umsatzsteuer aus; price_basis legt fest, ob der Preis als Brutto gilt (gross, Vorgabe — der Gesamtbetrag bleibt) oder als netto zuzüglich USt (net). Scope invoices:draft. Ohne Idempotency-Key erzeugt jeder Aufruf einen weiteren Beleg.

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": "convert_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`.
bodyNoJSON-Request-Body.
_idempotency_keyNoOptional. Geht als Header `Idempotency-Key` an die API: derselbe Wert mit demselben Aufruf liefert 24 Stunden lang die erste Antwort zurück, statt den Vorgang zu wiederholen. Bei einem Wiederholversuch denselben Wert schicken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries real weight and delivers: the quota is charged for the invoice draft, the invoice.created event fires, tax treatment can flip when the account's invoice settings change, and crucially that without an Idempotency-Key every call creates yet another document. That last point is exactly the non-obvious hazard an agent needs. Minor gap: no explicit warning about partial failures or how long a created follow-up doc can be amended afterward.

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?

The opening plan-tier line front-loads the most dangerous constraint, and the following sentences pack transitions, side effects and the idempotency warning without fluff. It is dense and long but almost every sentence carries unique information; the plan requirement is restated several times ('ab Pro', 'Ab Pro: Angebot → Rechnung', 'ab Business'), which is the main redundancy.

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 mutation tool with a nested body, no output schema and only two boolean annotations, the description covers return shapes, side effects, tier-gating errors, tax edge cases and idempotency behavior. Nothing an agent needs in order to invoke this safely is missing.

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 the schema already documents id, target, price_basis and the idempotency key thoroughly. The description reinforces price_basis (gross vs. net, only effective for a §19 invoice) and the idempotency key's 24-hour replay semantics, but adds little beyond what the schema states, so the baseline 3 applies.

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?

The description names a specific verb and resource ('Beleg umwandeln', 'Erzeugt den Folgebeleg') and enumerates the exact outputs (order_confirmation, delivery_note, invoice) plus the response types (SalesDocument vs. Invoice) and the invoice.created event. It further enumerates the legal chains (Angebot → AB/Lieferschein/Rechnung, AB → Lieferschein/Rechnung, Lieferschein → Rechnung), which distinguishes it clearly from create_sales_document and create_invoice_draft.

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 which source→target chains are permitted, which tier each requires ('ab Pro', 'ab Business', '403 plan_required'), and how the source document's status advances. It also routes the agent to list_sales_documents with `number` when only a document number is known instead of an id, giving an explicit alternative.

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