Skip to main content
Glama

Angebotsstatus setzen

set_offer_status
Idempotent

Record the customer's answer on an Angebot or Kostenvoranschlag of the connected facturo account: accepted, declined, or open again when it was set by mistake. Same switch as at facturo.at; nothing is sent to the client and the document stays unchanged. It takes the offer_number from get_recent_offers, and the change can be undone the same way. Creating an invoice or an Auftragsbestätigung from an offer marks it accepted by itself; an Auftragsbestätigung has no status.

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": {
      "offer_number": "<offer_number>",
      "status": "<status>"
    },
    "name": "set_offer_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
offer_numberYesFrom get_recent_offers or a finalize result, e.g. AN-2026-0012

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 (readOnlyHint=false, destructiveHint=false, idempotentHint=true) by disclosing that nothing is sent to the client, the document itself is unchanged, the effect matches the facturo.at switch, and the change is reversible the same way. That tells an agent exactly what a non-destructive write here does and does not touch.

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-loads the core action and states are listed early, then follows with behavioral caveats and edge cases. Dense but purposeful; 'Same switch as at facturo.at' is the one line that adds little for an agent without that UI context.

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 two-parameter mutation with no output schema, the description covers what changes, what does not (client notification, document contents), reversibility, and automation edge cases. Only the success/response expectation is left implicit, which is a minor gap.

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 50%, with offer_number already documented in the schema. The description adds provenance for it (get_recent_offers) and clarifies the semantics of the 'open' enum value — reopening a status set by mistake — which the enum alone does not convey.

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 verb and resource (record the customer's answer on an Angebot/Kostenvoranschlag) and enumerates the exact target states: accepted, declined, or open again. It also names the data source (offer_number from get_recent_offers), so an agent can distinguish it from finalize_offer or get_recent_offers at a glance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context (recording a customer's decision, reverting a mistake) and an important exclusion: creating an invoice or Auftragsbestätigung marks the offer accepted automatically, and an Auftragsbestätigung has no status, so this tool must not be used there. It stops short of naming a sibling for those flows, but the when-not guidance is genuinely useful.

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