Skip to main content
Glama

Angebot erstellen

finalize_offer
DestructiveIdempotent

Turn a previewed offer draft into the numbered Angebot, Kostenvoranschlag or Auftragsbestätigung. Only call it after the user has seen the preview and explicitly said yes. review_hash comes from the last preview_offer result; a stale hash is refused. Fails with the missing fields when something mandatory is missing. Calling it again for the same draft returns the document already created.

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": {
      "draft_id": "<draft_id>",
      "review_hash": "<review_hash>"
    },
    "name": "finalize_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYes
review_hashYesreview_hash of the preview the user confirmed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses error behavior (fails listing missing mandatory fields), hash-freshness validation, and the concrete meaning of idempotency (returns the already-created document). It stops short of saying what is actually destroyed or whether the document is emitted/downloaded versus merely stored, which matters given destructiveHint=true.

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 action, then the precondition, then parameter provenance, then failure and repeat-call behavior. Five short sentences, each carrying distinct information; slightly dense but no filler to cut.

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?

With no output schema, the description carries the burden of describing return behavior and does so ('returns the document already created'), and it covers the failure mode and the review_hash dependency. Only the nature of the 'destructive' side effect and any permission requirement are left unstated.

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 50%: review_hash is documented inline and the description reinforces it with the 'last preview_offer result' provenance and staleness rule. draft_id is left purely to the schema, though 'the same draft' and 'previewed offer draft' give some implicit meaning. Adequate but not full compensation for the uncovered parameter.

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?

States a specific transformation: a previewed offer draft becomes a numbered Angebot / Kostenvoranschlag / Auftragsbestätigung. This is clearly distinct from preview_offer, which it names explicitly, so an agent can tell the two apart without opening any schema.

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?

'Only call it after the user has seen the preview and explicitly said yes' gives an unambiguous precondition and implicitly names the alternative (preview_offer) that must precede it. The refusal of a stale hash and the idempotent re-call behavior further constrain when a call is valid.

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