Skip to main content
Glama

MaxRechnung

Beleg festschreiben

update_invoice_status
Destructive

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

Beleg festschreiben

Statusänderung, { "status": … } — keine weiteren Felder. sent: § 14-UStG-Pflichtcheck, danach unveränderlich (Korrekturen über POST /invoices/{id}/corrections). paid gibt es nur in Free und Pro, also mit den Keys des KI-Agenten: Im Business-Tarif ergibt sich der Status aus den Zahlungseingängen, paid wird dort mit 409 abgelehnt, die Zahlung erfasst POST /payments. Öffentliche Keys laufen immer im Business-Tarif. Scope 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": "update_invoice_status"
  }
}

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`.
bodyNoJSON-Request-Body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that `sent` triggers a §14-UStG compliance check and renders the invoice immutable afterwards, that corrections must go through `POST /invoices/{id}/corrections`, and that the required scope is `invoices:write`. The `409` rejection path is a concrete failure mode an agent would otherwise discover only by error.

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 but front-loaded and free of padding; every clause carries operational meaning. Minor deductions for the redundant repetition of the title ("Beleg festschreiben") and for leading with the plan-availability note rather than the core action.

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 two-parameter mutation with no output schema, the description covers side effects (irreversibility), error behavior (409), authentication/scope requirements, and the remediation path. Nothing an agent needs in order to invoke it safely is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns more by clarifying that the body carries only `status` and no other fields, and by explaining the plan-dependent semantics of each enum value. It still leaves the `id` vs. document-number distinction to the schema, which already handles it well.

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+resource (Statusänderung on an invoice via `{ "status": … }`) and defines exactly the two permitted values. It does not name a sibling tool for contrast, so the agent must infer differences from `update_invoice_draft` or `cancel_invoice` on its own, but the operation itself is unmistakable.

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?

Explicit when/when-not guidance: `sent` is allowed in every plan, `paid` only in Free and Pro, while Business-plan keys get a `409` and must use `POST /payments` instead. It even flags that public keys always run in Business, so an agent can pick the right path without trial and error.

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