lexware-mcp-server

Update Voucher

lexware_update_voucher

Idempotent

Update a bookkeeping voucher using its current version for optimistic locking; set an unchecked voucher's status to open during the update.

Instructions

Update a bookkeeping voucher with the current version for optimistic locking. If the existing voucher is unchecked, the update must transition voucherStatus to open.

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>",
      "body": "<body>"
    },
    "name": "lexware_update_voucher"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Voucher UUID
`body`	Yes	Voucher JSON with the current version field required for optimistic locking. If the existing voucher is unchecked, the update must transition voucherStatus to open; this constraint does not apply to vouchers already in other statuses.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv5.3.0Oct 5, 2026

changedInput schema / properties / body / description

Previous value: -"Voucher JSON with version field for optimistic locking"New value: +"Voucher JSON with the current version field required for optimistic locking. If the existing voucher is unchecked, the update must transition voucherStatus to open; this constraint does not apply to vouchers already in other statuses."

First observedv3.0.0May 26, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare the safety profile (not read-only, idempotent, not destructive), so the description's job is to add context. It does so by disclosing the optimistic-locking version requirement and the unchecked→open status transition constraint, which are non-obvious behavioral rules an agent must respect.

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?

Two tight sentences with the core action and the key constraint front-loaded. The second sentence duplicates the schema's body description, so there is minor redundancy but no wasted padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with a free-form body object (additionalProperties, no field guidance) and no output schema, the description covers the locking and status rules but leaves unanswered whether the body replaces or merges existing voucher fields, which matters for correct invocation.

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 description coverage is 100%, and the description essentially restates the body parameter's schema description rather than adding new semantics. Baseline 3 is appropriate since the schema already documents both parameters and their constraints.

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?

States a specific verb (update) and resource (bookkeeping voucher) and names the key mechanism (current version for optimistic locking). It is clear against siblings like lexware_get_voucher or lexware_create_voucher, though it does not explicitly name which sibling to use instead.

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?

Provides an important conditional rule (unchecked vouchers must transition to open), which implies when this tool applies. However, it gives no explicit when-to-use vs alternatives guidance, no prerequisites, and no exclusions beyond that one status case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server