Skip to main content
Glama
lazyants

lexware-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Contacts

lexware_list_contacts
Read-onlyIdempotent

Fetch contacts from Lexware Office with filters for name, email, number, vendor, or customer and pagination controls.

Instructions

List all contacts with optional pagination and filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter by name
pageNoPage number (0-indexed)
sizeNoResults per page (max 250)
emailNoFilter by email address
numberNoFilter by contact number
vendorNoFilter for vendors
customerNoFilter for customers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.0
    • removedInput schema / properties / archived
      Removed value: -{
-  "description": "Filter by archived status",
-  "type": "boolean"
-}
  2. First observedv3.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive. Description adds minimal behavioral context (pagination/filters) but lacks details like result set order or size limits. Not contradictory.

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?

Single sentence effectively communicates purpose and features. No wasted words; front-loaded with key actions.

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

Completeness2/5

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

Despite 7 parameters and no output schema, description omits response structure (e.g., paginated list metadata). Incomplete for a list operation with rich filtering.

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 covers 100% of parameters with descriptions. Tool description only summarizes 'optional pagination and filters', adding no meaning beyond schema.

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?

Description clearly states verb 'List' and resource 'contacts', with added features 'optional pagination and filters'. Distinguishes from sibling tools like lexware_get_contact for single contacts.

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?

No explicit guidance on when to use vs alternatives (e.g., lexware_get_contact for single contact). Usage is implied by name and context, but not stated.

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