BuchhaltungsButler MCP-Server

Overview Schema Source Related Servers Discussions Admin

Debitoren auflisten

bb_debtors_search

Read-onlyIdempotent

Lists debtor customer accounts with account number, name, and address to look up before assigning an outgoing invoice to a customer.

Instructions

Listet die Debitorenkonten des Mandanten in BuchhaltungsButler auf, also die Kundenkonten, mit Kontonummer, Name, Kundennummer und Anschrift. Gedacht zum Nachschlagen, bevor eine Ausgangsrechnung einem Kunden zugeordnet wird. Sachkonten, Zahlungskonten und Kreditoren liefert dieser Endpunkt nicht; dafür bb_postingaccounts_search. Einen Filter kennt er nicht, gesucht wird in der gelieferten Liste. Ohne ausdrückliches limit liefert die API nur 25 Zeilen.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Zeilen je Aufruf. Die API dokumentiert hier keine Obergrenze für limit. Wird der Aufruf mit 'invalid limit specified' abgelehnt, den Wert halbieren. Ohne ausdrückliches limit liefert die API nur 25 Zeilen; dieses Werkzeug sendet deshalb immer ein limit mit.
`offset`	No	Zahl der zu überspringenden Zeilen. Die zweite Seite einer Suche mit limit=100 holt offset=100.
`response_format`	No	'concise' liefert nur die Felder, die einen Datensatz erkennbar machen und den nächsten Schritt erlauben. 'detailed' liefert den Datensatz so, wie die BuchhaltungsButler-API ihn ausgibt. Mit 'concise' beginnen und nur für die wenigen Datensätze auf 'detailed' wechseln, die wirklich geprüft werden müssen. Dieses Feld ist serverseitig und geht nicht an die API.	concise

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`message`	No
`success`	Yes
`endpoint`	No
`limit_used`	No
`offset_used`	No
`more_possible`	No
`rows_returned`	No
`_contract_warnings`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely new behavior: no server-side filtering and a 25-row default when no limit is sent, plus the note that the tool always sends a limit. It stops short of describing pagination totals or response shape, which the output schema carries.

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?

Three tight sentences that front-load the purpose, then the alternative, then the paging caveat. The 25-row statement duplicates the schema's limit description, which is the only redundancy.

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?

With an output schema present, rich annotations, and fully documented parameters, the description covers everything an agent still needs to know: scope, exclusion, alternative route, no filtering, and the default page size.

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 limit/offset/response_format descriptions are already detailed in the schema, including the 25-row default and the 'invalid limit specified' halving advice. The description's limit remark largely repeats what the schema already says, so it adds little beyond the baseline.

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?

States a specific verb and resource ('Listet die Debitorenkonten des Mandanten') and enumerates the returned fields (Kontonummer, Name, Kundennummer, Anschrift). It explicitly excludes Sachkonten, Zahlungskonten and Kreditoren and names bb_postingaccounts_search as the sibling for those, so an agent can separate it from the many other *_search tools.

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?

Gives the concrete moment of use ('Nachschlagen, bevor eine Ausgangsrechnung einem Kunden zugeordnet wird') and an explicit an alternative-tool route ('dafür bb_postingaccounts_search'). It also warns that the endpoint has no filter, which is usage-limiting information an agent needs before calling.

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

Deploy Server