Skip to main content
Glama
office-books-mcp

office-books-mcp

by mjmirza

Search vouchers

list_vouchers
Read-only

Search sales and purchase invoices, credit notes, quotations and other vouchers by type, status, and date range. Returns metadata; use get_sales_document or get_voucher for full details.

Instructions

Search all vouchers (sales and purchase invoices, credit notes, quotations and more) by type, status and dates. Returns metadata. Use get_sales_document or get_voucher for full details.

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": {
      "voucherType": "<voucherType>",
      "voucherStatus": "<voucherStatus>"
    },
    "name": "list_vouchers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo0-based page index
sizeNoPage size, 1 to 250, Lexware default 25
archivedNo
contactIdNoLexware resource id (UUID)
voucherTypeYes
voucherDateToNo
voucherNumberNo
voucherStatusYes'overdue' cannot be combined with other status values
voucherDateFromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds meaningful context beyond that: results are metadata only, not full document bodies, which is the single most important behavioral fact for a search tool with no output schema. Pagination defaults and result ordering are left unstated.

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?

Three short sentences with no padding: what it does, what it returns, and where to go for more. The most important scoping fact (metadata only) is stated up front.

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 nine-parameter list tool with no output schema, the description covers the core search dimensions and the return-payload distinction, but omits filtering options like contactId and voucherNumber, ignores pagination controls (size max 250, default 25), and never mentions the required-parameter constraint on type and status.

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 44%, so the description must carry weight. It names type, status, and dates, mapping to voucherType, voucherStatus, and voucherDateFrom/To, but says nothing about contactId, voucherNumber, archived, page, or size, leaving several filters and all pagination semantics undocumented.

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 (search) and resource (vouchers), enumerates the voucher kinds covered, and names the filter dimensions (type, status, dates). It also explicitly distinguishes itself from get_sales_document and get_voucher as the summary-level vs. detail-level tools.

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?

Explicitly routes the agent to get_sales_document or get_voucher when full details are needed, which is the key decision point between these siblings. It stops short of stating when not to use it (e.g. for contacts/articles) or prerequisites, but the primary alternative is covered.

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