Skip to main content
Glama
office-books-mcp

office-books-mcp

by mjmirza

Get contact

get_contact
Read-only

Read one Lexware contact by UUID to return addresses, email addresses, and phone numbers for bookkeeping lookups.

Instructions

Read one contact with addresses, email addresses and phone numbers.

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

Input Schema

NameRequiredDescriptionDefault
idYesLexware resource id (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds what the payload includes (addresses, emails, phones), but says nothing about behavior when the contact is missing or unauthorized, and no output schema exists to fill that gap.

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?

One short sentence with the verb and resource front-loaded and zero filler. The parenthetical enumeration of returned fields is the only added weight and it earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-record read with one fully-described UUID parameter and read-only annotations, the definition covers what the tool returns and is sufficient to invoke it correctly. Only error/not-found behavior is unstated, a minor gap given the tool's simplicity.

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?

The single 'id' parameter is fully documented in the schema, including UUID format and pattern, so the schema carries the load. The description adds no meaning beyond that (e.g., how to obtain the id), which is acceptable at 100% coverage but not additive.

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 states a specific verb ('Read') and resource ('one contact') and enumerates the embedded data returned (addresses, email addresses, phone numbers), so an agent can distinguish it from a bulk listing. It stops short of naming a sibling such as list_contacts, so the contrast is only implied.

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?

'Read one contact' implies usage for single-record retrieval, which implicitly contrasts with a list operation, but there is no explicit when-to-use or when-not-to-use statement, nor any precondition such as needing a known UUID.

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