Unofficial Lexware Office MCP Server

Overview Schema Source Related Servers Discussions Admin

get_voucher

Read-only

Read one bookkeeping voucher by id or document number to retrieve booked amounts, tax type, line posting categories, contact, and version.

Instructions

Read one bookkeeping voucher, by id or by its document number.

One API call. Returns the booked amounts, tax type, the posting category of every line, the contact and the version.

Prefer the id. A number is unique only by convention, and search_vouchers finds one across every document type.

For whether it has been paid, use get_payments with the same id.

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

Input Schema

Name	Required	Description	Default
`voucher_id`	No	The voucher's Lexware id, from search_vouchers. Give this or voucher_number, not both.
`voucher_number`	No	The number printed on the document, for example 'RE-2026-014'. Use this when that is all you have.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.8.3Nov 9, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real behavioral context: a single API call, and precisely which fields come back (booked amounts, tax type, per-line posting category, contact, version). It also warns that voucher numbers are only unique by convention, which is a genuine reliability caveat. It stops short of describing error behavior or what happens when neither identifier resolves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short declarative sentences, front-loaded with the core action, then return payload, then parameter preference, then the sibling hand-off. No filler and no repetition of the schema.

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?

There is no output schema, so the description carries the return-shape burden and does so by enumerating the key returned fields including version. Combined with the routing to search_vouchers and get_payments, an agent has everything needed to call it correctly.

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, but the description adds a preference rule the schema does not encode: use the id because a number is unique only by convention. That meaningfully disambiguates the mutual-exclusivity the schema merely states.

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?

Opens with a specific verb and resource ('Read one bookkeeping voucher') plus the two addressing modes (id or document number). It is immediately distinguishable from the sibling search_vouchers, which is named as the multi-type lookup alternative.

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?

Explicit routing: prefer the id, use search_vouchers to find one across document types, and use get_payments with the same id for payment status. Both the when-to-use and the when-to-use-something-else cases are stated.

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