BuchhaltungsButler MCP-Server

Overview Schema Source Related Servers Discussions Admin

Buchung stornieren

bb_postings_cancel

Destructive

Cancel a single posting line in BuchhaltungsButler to correct a fixed posting. Check fixed status first; fixed creates a reversal, unfixed removes the line.

Instructions

Storniert in BuchhaltungsButler eine einzelne Buchungszeile. Zu nehmen, wenn eine festgeschriebene Buchung zu korrigieren ist; eine nicht festgeschriebene entfernen bb_postings_unconfirm_for_receipt, bb_postings_unconfirm_for_transaction und bb_postings_unconfirm_free rückstandslos. War die Buchung festgeschrieben, entsteht eine dauerhaft sichtbare Stornobuchung, sonst verschwindet sie; die Antwort unterscheidet beides nicht, deshalb vorher fixed mit bb_postings_search lesen. Storniert genau eine Zeile: eine Splitbuchung mit fünf Zeilen braucht fünf Aufrufe, und ein Zwischenstand ist ein unausgeglichener Buchungsstand. Entfernt Daten aus dem echten Mandanten von BuchhaltungsButler: die genannte Buchungszeile. Die betroffenen Datensätze vorher lesen und dem Nutzer vorlegen.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`posting_id_by_customer`	Yes	Die mandantenbezogene Nummer der zu stornierenden Buchungszeile, zu finden über bb_postings_search. Das Feld fixed derselben Zeile sagt vorher, welche der beiden Wirkungen eintritt: Storno bei '1', ersatzloses Entfernen bei '0'. In Suchergebnissen erscheint sie als String; hier ohne Anführungszeichen übergeben.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`message`	No
`removed`	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.6/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and non-idempotent, and the description adds meaningfully beyond that: a fixed posting produces an irreversible, permanently visible Stornobuchung whereas a non-fixed one disappears, and the API response does not distinguish the two. It also discloses the split-posting constraint (five lines = five calls, intermediate state is unbalanced) and that data is removed from the real tenant.

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?

Dense but front-loaded: purpose first, then condition, then effects, then constraints. Minor redundancy in restating the removal target ('die genannte Buchungszeile') after the purpose sentence, but no filler.

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?

An output schema exists so return values need not be explained, and the description nonetheless flags the one thing the output hides (that it does not tell the caller which of the two effects occurred). With the pre-read requirement, single-line scope, and split warning, an agent has everything needed to call this safely.

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 the single parameter is already fully documented, including the fixed=1 vs 0 consequence and the string-vs-integer search-result caveat. The description repeats rather than extends this, so the baseline 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 ('Storniert ... eine einzelne Buchungszeile') and immediately scopes it to exactly one line, distinguishing it from the unconfirm siblings by name. An agent can tell what this does and what it does not do without opening the 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 when-to-use rule ('wenn eine festgeschriebene Buchung zu korrigieren ist') and routes the non-fixed case to three named alternatives. It even warns that a fixed line leaves a permanent reversal entry while a non-fixed one vanishes, so the agent knows to pre-read 'fixed' via bb_postings_search before choosing.

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

Deploy Server