Skip to main content
Glama

MaxRechnung

Sammelrechnung aus Belegen

merge_sales_documents
Destructive

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

Sammelrechnung aus Belegen

Eine Rechnung aus mehreren Belegen desselben Empfängers und derselben Währung (z. B. alle Lieferscheine eines Monats): je Beleg eine Überschriftszeile, dann dessen Positionen; alle Bezüge in der Bezugszeile. Reihenfolge der Positionen = Reihenfolge der ids. Kopf, Steuer und Rabatt kommen aus dem ersten Beleg — deshalb müssen Preismodus (netto/brutto), Steuerregelung und Rabatt bei allen gleich sein (ein Rabatt nur als gleicher Prozentsatz). Kein Beleg darf schon abgerechnet sein, keiner Vorbeleg eines anderen (etwa AB und ihr Lieferschein). Die Belege gelten danach als erledigt und verweisen auf die Rechnung; Vorbelege der Kette rücken mit. Antwort Invoice (Entwurf). Ab Business. Scope invoices:draft.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "merge_sales_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.1/5.0
Behavior3/5

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

Annotations already flag this as a mutation (readOnlyHint=false, destructiveHint=true), and the description usefully adds the concrete side effects: the documents are marked as settled afterwards, reference the new invoice, and upstream predecessors of the chain move along with them. It also discloses required scope invoices:draft and the draft return type. The extra context is real but limited to the same side-effect family the annotations already signal.

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 text is dense and front-loads the plan gate before the actual operation, and every constraint earns its place. Minor waste exists: the title line is repeated verbatim inside the description and 'Ab Business' appears twice (opening line and closing line).

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 complex, destructive multi-document merge with no output schema, the description covers preconditions, side effects on source documents and their predecessor chains, plan gating, auth scope, and return type. An agent has everything needed to decide whether the call will succeed and what it changes.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds genuine meaning the schema cannot convey: the order of line items follows the order of the ids array, and header, tax and discount are taken from the first document — which is precisely why all documents must share those attributes. That is essential semantics for correct invocation.

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 names a specific operation and resource: one invoice built from multiple documents (Belege) of the same recipient and currency, with one header line per document followed by its line items. This clearly distinguishes it from single-document creation or conversion siblings, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

Preconditions are stated in detail: same recipient, same currency, identical price mode (net/gross), tax rule and discount (only as an identical percentage), no already-billed document, no document that is a predecessor of another. The Business-plan requirement and the plan_required error are also called out. What is missing is an explicit pointer to the alternative tool for the single-document case.

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