BuchhaltungsButler MCP-Server

Overview Schema Source Related Servers Discussions Admin

Debitorenkonto anlegen

bb_debtors_create

Creates a customer account in BuchhaltungsButler before you assign an outgoing invoice. Omit postingaccount_number to get the next free number; writes real data and cannot be undone via API.

Instructions

Legt ein Debitorenkonto, also ein Kundenkonto, in BuchhaltungsButler an. Gedacht für einen neuen Kunden, bevor ihm eine Ausgangsrechnung zugeordnet wird. Ohne postingaccount_number vergibt BuchhaltungsButler die nächste freie Nummer und nennt sie in der Antwort. Mehrere Konten in einem Aufruf legt bb_debtors_create_batch an; Lieferanten sind Kreditoren und gehören zu bb_creditors_create. Schreibt in die echten Buchhaltungsdaten von BuchhaltungsButler. Die API bietet keinen Endpunkt, das rückgängig zu machen.

Input Schema

TableJSON Schema

Name	Required	Description
`bic`	No	BIC der Bankverbindung, zum Beispiel BYLADEM1001.
`zip`	No	Postleitzahl, zum Beispiel "28195".
`city`	No	Ort, zum Beispiel Bremen.
`iban`	No	IBAN der Bankverbindung, zum Beispiel DE02120300000000202051.
`name`	Yes	Name des Kundenkontos, zum Beispiel Musterkunde GmbH.
`email`	No	E-Mail-Adresse, zum Beispiel rechnung@beispiel.de.
`street`	No	Straße und Hausnummer, zum Beispiel Hauptstraße 12.
`country`	No	Land, zum Beispiel Deutschland oder DE.
`sales_tax_id`	No	Umsatzsteuer-Identifikationsnummer, zum Beispiel DE123456789.
`customer_number`	No	Kunden- oder Lieferantennummer des Mandanten.
`contact_person_name`	No	Name der Ansprechperson, zum Beispiel Maria Schmidt.
`postingaccount_number`	No	Kontonummer des neuen Debitorenkontos als Zeichenkette. Ohne Angabe vergibt BuchhaltungsButler die nächste freie Nummer. Belegte Nummern zeigt bb_debtors_search.
`additional_address_line`	No	Zusätzliche Adresszeile, zum Beispiel Gebäude B.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`created`	No
`message`	No
`success`	Yes
`endpoint`	No
`reversal`	No
`_contract_warnings`	No
`fields_not_returned`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare a non-read-only, non-destructive, non-open write, but the description adds material context beyond them: writes go to real live accounting data, and the API offers no endpoint to undo the operation. It also discloses the auto-numbering side effect and that the assigned number is returned in the response.

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?

Six tight sentences, each carrying distinct information: purpose, usage context, default behavior, alternatives, write scope, irreversibility. Purpose is front-loaded and nothing is padding.

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?

For a 13-parameter mutation tool with full schema coverage, an output schema, and safety annotations, this description covers everything an agent needs: what it does, when to pick it versus siblings, and the irreversible-write risk. No gap remains for correct invocation.

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 100% across all 13 parameters, so the schema already carries parameter meaning and 3 is the baseline. The description's note that omitting postingaccount_number triggers automatic numbering duplicates what the schema's own description says rather than adding new syntax or constraints.

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 ('legt ein Debitorenkonto, also ein Kundenkonto, in BuchhaltungsButler an') and immediately disambiguates the German term. It names the sibling tools it is not (bb_debtors_create_batch, bb_creditors_create), so the agent can select correctly without opening schemas.

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?

Explicit context for use ('für einen neuen Kunden, bevor ihm eine Ausgangsrechnung zugeordnet wird') plus clear routing to alternatives: batch creation for multiple accounts and bb_creditors_create for suppliers. Both when-to-use and when-to-use-something-else are covered.

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

Deploy Server