Skip to main content
Glama

MaxRechnung

Neue Fassung eines Angebots

revise_quote

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

Neue Fassung eines Angebots

Für ein versendetes (sent) oder abgelehntes (declined) Angebot: legt eine Kopie als Entwurf an (neue Angebotsnummer, heutiges Datum) und setzt am alten Angebot superseded_by. Das alte Angebot gilt damit als ersetzt; sein Annahme-Link bleibt erreichbar, nimmt aber keine Antwort mehr an. Den Annahme-Link erzeugt nur der Mailversand aus der App; die API legt keinen an und gibt keinen aus. Entwürfe (direkt änderbar), angenommene, erledigte und bereits ersetzte Angebote: 409 conflict. Ab Pro. Scope invoices:draft. Ohne Idempotency-Key legt jeder Aufruf eine weitere Fassung an.

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

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`.
_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.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes far beyond them by disclosing the side effect on the source document (`superseded_by`), that the old acceptance link stays reachable but stops accepting responses, that the API never issues an acceptance link, and that omitting `Idempotency-Key` produces a new version per call. These are exactly the consequences an agent needs before triggering an irreversible-looking state change.

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?

Front-loaded with the plan gate and the core semantics, and nearly every sentence carries operational information. Minor waste: the plan requirement is stated twice ('Tarif: ab Pro' at the start and 'Ab Pro.' near the end), and the title line repeats the description's opening.

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 what an agent cannot get from structured fields: eligibility states, the 409 conflict set, plan and scope requirements, idempotency consequences, and the fact that no acceptance link is returned. Nothing material is missing for a correct invocation.

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 adds value by spelling out the consequence of omitting `_idempotency_key` ('legt jeder Aufruf eine weitere Fassung an'), which the schema itself only describes in terms of the 24-hour replay window. It adds no further detail about `id` beyond the schema's UUID-vs-number note, but that note is already thorough.

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?

Names a specific verb and resource ('legt eine Kopie als Entwurf an … neue Angebotsnummer, heutiges Datum') and precisely distinguishes it from an in-place edit by explaining that a copy is created and the original gets `superseded_by`. It also disambiguates from draft editing ('Entwürfe (direkt änderbar)'), so an agent knows this is not the tool for editing a 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?

Gives explicit preconditions ('Für ein versendetes (`sent`) oder abgelehntes (`declined`) Angebot') and explicit exclusions with the resulting error ('Entwürfe …, angenommene, erledigte und bereits ersetzte Angebote: `409 conflict`'). It also states the plan gate (`plan_required` below Pro) and the scope `invoices:draft`, leaving little to infer before calling.

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