buchpilot-mcp

list_contacts

Retrieve contacts from your accounting system with filters for name, email, or role (customer/vendor). Quickly access specific contacts needed for invoicing and bookings.

Instructions

Listet Kontakte auf mit optionalen Filtern. Lists contacts with optional filters.

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

Name	Required	Description
`name`	No	Nach Name filtern
`email`	No	Nach E-Mail filtern
`role`	No	Nach Rolle filtern
`limit`	No	Maximale Anzahl
`backend`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Apr 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as pagination, sorting, authentication needs, or side effects. It only states the basic function without additional context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and bilingual, which is efficient but redundant. It front-loads the purpose but lacks structure or detail. Every sentence earns its place but could be more informative.

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?

Given the absence of an output schema, the description should explain return values or behavior. It does not mention what the list returns, pagination limits, or how the filters combine. The tool has 5 parameters but the description provides minimal context.

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 high (80%), so the baseline is 3. The description says 'optional filters' but adds no specifics beyond what the parameter descriptions already provide. It does not enhance understanding of parameters.

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 clearly states the tool lists contacts with optional filters, distinguishing it from sibling tools like get_contact (single) and list_invoices (different resource). It is not a tautology and gives a specific action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives (e.g., get_contact for a single contact, or other list tools). The description only mentions optional filters but doesn't explain scenarios or exclusions.

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

Deploy Server