Skip to main content
Glama
Sign In
office-books-mcp

office-books-mcp

by mjmirza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List contacts

list_contacts
Read-only

Lists customers and vendors from Lexware Office bookkeeping data and filters them by name, email, number, or role.

Instructions

List customers and vendors. Filter by name (min 3 chars), email, customer or vendor number, or role.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
pageNo0-based page index
sizeNoPage size, 1 to 250, Lexware default 25
emailNo
numberNoCustomer or vendor number
vendorNo
customerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.2/5.0
Behavior2/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 no behavioral context beyond that. It says nothing about pagination defaults, result caps, ordering, or what a caller gets back when no filters are supplied, which matters for a list operation whose page/size parameters drive behavior.

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 short sentences with the resource stated first and filters second; no filler. Slightly marred by the dangling 'role' mention, which adds words without adding a usable parameter mapping.

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 7-parameter, zero-required list tool with no output schema, the definition covers what can be filtered but omits how filters interact, whether results are paginated by default, and what the objects contain. It is adequate to make a first call but incomplete for predictable use.

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 only 43%, and the description does helpfully gloss otherwise bare parameters: name (min 3 chars), email, and especially 'customer or vendor number' for the ambiguous `number` field. However, it introduces 'role' which maps to no parameter, and it leaves page/size semantics (default 25, max 250) entirely to the schema.

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 and resource ('List customers and vendors') so the agent immediately knows this returns contact records, distinguishing it from list_vouchers/list_articles by resource name. It does not explicitly contrast with get_contact, but the list-vs-get distinction is clear from the verb.

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?

Implied guidance only: the description enumerates filter options, which suggests 'use this when searching/browsing contacts', but it never says when to prefer this over get_contact for a single known contact, nor whether filters combine (AND/OR) or are all optional.

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

Deploy Server

Other Tools