Unofficial Lexware Office MCP Server

Overview Schema Source Related Servers Discussions Admin

get_contact

Read-only

Retrieve a complete contact record by its Lexware ID, including roles, addresses, emails, phone numbers, note, and version for accurate updates.

Instructions

Read one contact in full, by id.

Returns the complete record: roles and their numbers, billing and shipping addresses, all email addresses and phone numbers, the note and the version. Costs one API call.

Use search_contacts when you have a name rather than an id. Read this before updating a contact, because update_contact needs the version it reports.

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": {
      "contact_id": "<contact_id>"
    },
    "name": "get_contact"
  }
}

Input Schema

Name	Required	Description	Default
`contact_id`	Yes	The contact's Lexware id, as returned by search_contacts or referenced by a voucher.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.8.3Nov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations only supply readOnlyHint=true; the description adds real context beyond that: the exact record contents returned (roles, addresses, emails, phones, note, version) and the cost of one API call. It stops short of stating failure behavior for an unknown id, so it is not quite a 5.

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 paragraphs, front-loaded with the purpose, then the return shape, then the routing and prerequisite. Every sentence carries distinct information, including the otherwise easy-to-omit API cost note.

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, and the description compensates by enumerating the returned fields, so the agent knows what it gets. For a single-parameter read tool with one annotation, nothing needed for correct invocation is missing.

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% and the single contact_id parameter is already documented as a Lexware id returned by search_contacts or referenced by a voucher. The description's 'by id' phrasing adds no format or validation detail beyond the schema, so the baseline 3 applies.

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?

The opening line states a specific verb and resource with scope ('Read one contact in full, by id'), which immediately separates it from the sibling search_contacts and from get_article/get_voucher which target other resources.

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?

It gives explicit routing ('Use search_contacts when you have a name rather than an id') and a sequencing rule ('Read this before updating a contact, because update_contact needs the version it reports'), covering both the alternative and the prerequisite.

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