Skip to main content
Glama

MaxRechnung

Belegstatus setzen

update_sales_document_status

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

Belegstatus setzen

Angebot: draft, sent, accepted, declined; AB und Lieferschein: draft, sent, done. Abgelaufene Angebote (valid_until überschritten, Status sent) zeigt die Liste als „abgelaufen“ an, gespeichert bleibt sent. Ein Angebot kehrt nicht zu draft zurück, und ein ersetztes Angebot (superseded_by) ändert seinen Status nicht mehr (409 conflict). Angebote ab Pro; der Status einer Auftragsbestätigung oder eines Lieferscheins ab Business (403 plan_required). 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": "update_sales_document_status"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false) the description discloses failure modes and invariants an agent cannot get from structured fields: `plan_required`/`403` gating per document type, `409 conflict` for superseded quotes, no transition back to `draft`, and the fact that expired quotes stay stored as `sent` even though the list renders them as expired. That is exactly the mutation-safety context the annotations leave open.

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?

The plan constraint is front-loaded, which is good, but the line 'Belegstatus setzen' merely restates the name/title, and the plan gating is effectively stated twice (top line, then again at the end with the Business tier). Long parenthetical sentences with error codes make it dense rather than scannable.

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 mutating tool with no output schema and a nested body object, the business rules are covered thoroughly. The notable gap is the return value and side effects — it never says what the call returns or whether setting `sent` triggers anything customer-facing, which matters for a status mutation.

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, but the description adds meaning the bare enum cannot convey: which of `draft`/`sent`/`accepted`/`declined`/`done` are legal depends on whether the document is a quote, an order confirmation, or a delivery note. It does not clarify whether `body` carries anything besides `status`.

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 verb and resource ('Belegstatus setzen') and scopes it to the status field of a sales document, which separates it from the general 'update_sales_document' sibling. It does not explicitly contrast itself with 'update_invoice_status' or 'update_sales_document', so the differentiation is inferred rather than stated.

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?

It gives concrete preconditions (Pro plan for quotes, Business for order confirmations and delivery notes, scope `invoices:draft`) and which status values apply to which document type, which is real usage guidance. It never says when to prefer this tool over `update_sales_document` or how to handle the case where a caller wants to change other fields too, so the when-not side is absent.

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