Skip to main content
Glama

Angebot als Vorschau

preview_offer
Destructive

Preview an Angebot, Kostenvoranschlag or Auftragsbestätigung for the connected facturo account; the user sees it as a card. The first call creates an Entwurf the user also sees at facturo.at, later calls with draft_id change it: pass only what changes, the rest stays. Call it again after every change the user asks for; finalize_offer needs the review_hash of the card the user confirmed. For an Auftragsbestätigung pass source_offer_number; items, client, VAT and texts come from the source and can be overridden. The result lists what is still missing.

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

Input Schema

NameRequiredDescriptionDefault
itemsNo
clientNoThe invoice recipient. The name is required for the first preview of a draft; the real invoice needs the address.
draft_idNoHandle from an earlier preview_offer result; pass it to change that draft instead of starting a new one.
fusstextNoText below the totals; defaults to the account's standard text
kopftextNoText above the items; defaults to the account's standard text
vat_rateNoPercent for tax_exempt 'show', default 20
client_idNoA client of the connected account (from search_clients) instead of client.
offer_dateNoYYYY-MM-DD, default today
tax_exemptNo'show' prints USt at vat_rate, 'exempt' prints no USt (Kleinunternehmer, reverse charge). Leave it out to take the account's usual setting for this client; the result names what was applied.
discount_typeNoGesamtrabatt on the whole document, deducted as its own line below the items (VAT is computed on the reduced amount). 'percentage' = discount_value is a percent of the net item total, 'fixed' = discount_value is an EUR amount (in the draft's price mode). Requires discount_value. Set it when the user grants a discount/Nachlass/Aktionscode on the whole invoice or offer; never bill a discount as a negative item. 'none' clears a discount set earlier. Not available on an Anzahlungsrechnung (the deposit share replaces it); a Storno inherits the cancelled invoice's discount automatically.
document_typeNo'angebot' (default), 'kostenvoranschlag' or 'auftragsbestaetigung'. An Auftragsbestätigung confirms an accepted Angebot/KV: pass source_offer_number and the draft is prefilled from it.
validity_dateNoYYYY-MM-DD, default offer_date + 30 days
discount_valueNoDecimal as string: the percent ('25') or EUR amount ('100') per discount_type. Must be above 0, a percentage at most 100.
reference_linesNoReference lines under the address, one per line
signature_blockNoAuftragsbestätigung only: 'Ort, Datum' and 'Unterschrift Auftraggeber' lines under the closing text so the customer can countersign. Default true; set false only when the user wants no signature lines. Ignored on an Angebot or Kostenvoranschlag.
prices_include_vatNoUnit prices are gross (default false, net)
source_offer_numberNoNumber of the finalized Angebot/KV an Auftragsbestätigung confirms (from get_recent_offers).
discount_descriptionNoLabel printed on the discount line, e.g. 'Rabatt' (default), 'Rabatt Aktionscode START25', 'Treuebonus'. The percentage or amount is printed next to it automatically, so leave it out of the label.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly=false and destructive=true, so the mutation profile is known; the description adds the important context that this persists a draft visible to the user at facturo.at and that subsequent calls are partial updates. It does not explain what is overwritten or how a draft is abandoned (that lives in discard_draft), which is the main remaining behavioral gap.

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: purpose first, then the create/modify lifecycle, then the finalize handoff, then the Auftragsbestätigung variant. A few clauses are packed (the VAT/text inheritance sentence), but nothing is redundant filler.

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 an 18-parameter, nested-object tool with no output schema, the description covers the draft lifecycle, the review_hash handoff, and prefill behavior. It still leaves the exact shape of the preview result implicit (beyond 'lists what is still missing'), which matters given there is no output schema.

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 already 94%, so the schema carries most parameter meaning. The description still adds non-schema semantics: draft_id as a handle from a prior result, source_offer_number triggering prefill with overridable items/client/VAT/texts, and the 'result lists what is still missing' feedback loop.

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 opens with a specific verb ('Preview') and the concrete resource (Angebot, Kostenvoranschlag, Auftragsbestätigung) and states the user-visible outcome ('the user sees it as a card'). It implicitly separates itself from preview_invoice by enumerating only offer-type documents, though it never names that sibling explicitly.

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?

It gives explicit lifecycle rules: the first call creates an Entwurf, later calls with draft_id modify it, 'pass only what changes, the rest stays', and 'call it again after every change the user asks for'. It also states the handoff condition to finalize_offer (needs the review_hash of the confirmed card) and the prefill path for an Auftragsbestätigung via source_offer_number.

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