BuchhaltungsButler MCP-Server

Overview Schema Source Related Servers Discussions Admin

Sachkonto anlegen

bb_postingaccounts_create

Creates a new general ledger account in BuchhaltungsButler, inheriting tax settings from a parent account template. Use it to add custom expense accounts to the chart of accounts.

Instructions

Legt ein neues Sachkonto im Kontenrahmen des Mandanten in BuchhaltungsButler an. Gedacht für ein eigenes Aufwandskonto, etwa 4931 für Softwarelizenzen. Das neue Konto erbt seine Eigenschaften, darunter die Steuerbehandlung, vom Vorlagekonto parent_postingaccount_number; dieses vorher mit bb_postingaccounts_search heraussuchen. Kundenkonten legt bb_debtors_create an, Lieferantenkonten bb_creditors_create, Zahlungskonten bb_payment_accounts_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
`name`	Yes	Bezeichnung des neuen Sachkontos, zum Beispiel Softwarelizenzen Cloud.
`postingaccount_number`	Yes	Nummer des neuen Sachkontos als ganze Zahl, zum Beispiel 4931. Sie muss frei sein und in den Kontenrahmen des Mandanten passen; belegte Nummern zeigt bb_postingaccounts_search.
`parent_postingaccount_number`	Yes	Nummer des Vorlagekontos als ganze Zahl, zum Beispiel 4930. Das neue Konto erbt dessen Eigenschaften, etwa die Steuerbehandlung. Nachschlagen mit bb_postingaccounts_search.

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.5/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, openWorld=true, destructive=false. The description meaningfully adds that it writes to real accounting data and that the API exposes no endpoint to undo the creation — a genuine irreversibility warning that isn't in the annotations.

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?

What the tool does is front-loaded, followed by use case, inheritance/lookup requirement, alternatives, and side effects in an efficient sequence. Every sentence carries distinct information with no 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?

With an output schema present, return values need no explanation. Prerequisites, exclusions, sibling routing and irreversibility are all covered, leaving nothing an agent needs to call this correctly.

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%, so all three parameters are already documented with examples. The description restates the inheritance-from-parent semantic but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 neues Sachkonto im Kontenrahmen des Mandanten an) and explicitly distinguishes this from customer, supplier and payment accounts by naming the sibling tools that handle those cases. An agent can select it without opening any schema.

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 an explicit use case (eigenes Aufwandskonto, e.g. 4931 für Softwarelizenzen), names the alternative tools with their conditions (bb_debtors_create, bb_creditors_create, bb_payment_accounts_create), and states the prerequisite of looking up the parent account with bb_postingaccounts_search first.

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

Deploy Server