Skip to main content
Glama
lazyants

lexware-mcp-server

by lazyants

List Voucherlist

lexware_list_voucherlist
Read-onlyIdempotent

Search and filter across all voucher types in Lexware to find invoices, credit notes, quotations, and other documents by criteria like date, status, contact, and number.

Instructions

Search and filter across all voucher types in Lexware. This is the main way to find invoices, credit notes, quotations, and other voucher types.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (0-indexed)
sizeNoResults per page (max 250)
archivedNoFilter by archived status
contactIdNoFilter by contact UUID
voucherTypeNoVoucher type(s), comma-separated, or "any" for no type filter (default). Values: invoice, creditnote, orderconfirmation, quotation, deliverynote, downpaymentinvoice, dunning, purchaseinvoice, purchasecreditnoteany
createdDateToNoFilter by creation date to (yyyy-MM-dd)
voucherDateToNoFilter vouchers to date (ISO, e.g. "2024-12-31")
voucherNumberNoFilter by voucher number
voucherStatusNoVoucher status(es), comma-separated, or "any" for no status filter (default). Values: draft, open, overdue, paid, paidoff, voided, accepted, rejected, uncheckedany
createdDateFromNoFilter by creation date from (yyyy-MM-dd)
voucherDateFromNoFilter vouchers from date (ISO, e.g. "2024-01-01")
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, fully covering safety and behavioral traits. The description adds minimal context beyond saying it searches across all voucher types, which is already implied by the name.

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?

Two sentences that front-load the action and are free of unnecessary words. Every sentence earns its place.

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?

Given the 11 optional parameters and no output schema, the description is adequate but could mention returned data structure or pagination behavior. It leaves some gaps for a comprehensive understanding.

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 100%, with each parameter having a clear description. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 uses the verb 'search and filter' and specifies the resource 'all voucher types'. It clearly states the tool's purpose but does not differentiate from the sibling 'lexware_list_vouchers', which may cause confusion.

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?

The description implies usage by calling it 'the main way to find invoices, credit notes, quotations', but it does not explicitly state when to use this tool versus alternatives or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lazyants/lexware-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server