Skip to main content
Glama

MaxRechnung

Rechnungskorrektur anlegen

create_correction
Destructive

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

Rechnungskorrektur anlegen

Erstellt einen Korrektur-Entwurf (Nummernkreis KR-) mit Pflichtbezug auf die festgeschriebene Rechnung {id}. Positionen werden übernommen — für eine Gutschrift die Einzelpreise negativ setzen (PATCH), dann festschreiben.

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": "create_correction"
  }
}

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`.
_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

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, which the description does not contradict), it discloses that only a draft is produced, that line items are copied automatically, and that a credit note requires negative unit prices set via PATCH before finalizing. Missing: permission requirements, and whether the draft is reversible or what state it lands in after finalization.

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?

Short and mostly front-loaded, but the title line "Rechnungskorrektur anlegen" duplicates the title field and the plan-availability line sits ahead of the actual behavior, pushing the substantive content back slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter create tool the coverage is decent, and the create-then-PATCH-then-finalize workflow is useful context. However, with no output schema the description never says what the call returns — notably the new draft's id, which the described PATCH step depends on.

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%, including the note that `id` is the internal UUID and not the document number, and the idempotency-key behavior. The description only reinforces that the referenced invoice must be finalized; it adds no syntax or format detail beyond the schema, so 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 names a concrete verb and resource ("Erstellt einen Korrektur-Entwurf") and pins down the distinctive traits: the KR- number range and the mandatory reference to a finalized invoice. That implicitly separates it from draft-invoice creation 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 Guidelines3/5

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

Usage is implied rather than stated: you reach for this when you need a correction or credit note against an already finalized invoice. There is no explicit when-not guidance and no mention of alternatives such as cancelling the invoice instead, so the agent must infer the boundary.

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