BuchhaltungsButler MCP-Server

Overview Schema Source Related Servers Discussions Admin

Kostenstelle überschreiben

bb_cost_locations_update

DestructiveIdempotent

Overwrites the name of an existing cost center in BuchhaltungsButler while its code and linked postings stay unchanged. Read the record before and after with bb_cost_locations_search, since changes cannot be undone.

Instructions

Überschreibt die Bezeichnung einer Kostenstelle in BuchhaltungsButler. Gedacht für eine berichtigte Bezeichnung. Der code bleibt unverändert; er ist der Identifikator und lässt sich nicht ändern. Buchungen, die auf diese Kostenstelle verweisen, bleiben erhalten und erscheinen danach unter der neuen Bezeichnung. Die Antwort bestätigt die neue Bezeichnung nicht, deshalb den Stand vorher und nachher mit bb_cost_locations_search lesen. Überschreibt Stammdaten im echten Mandanten von BuchhaltungsButler. Die API liefert die vorherigen Werte nicht zurück; ohne vorher gelesenen Datensatz ist die Änderung nicht rückgängig zu machen.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes	Code der zu ändernden Kostenstelle, zum Beispiel abc123. Er ist der Identifikator und lässt sich nicht ändern. Nachschlagen mit bb_cost_locations_search.
`name`	Yes	Neue Bezeichnung der Kostenstelle, zum Beispiel Vertrieb Nord. Sie ersetzt die bisherige vollständig.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`changed`	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.4/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that bookings referencing the cost center are preserved and re-labelled, that the response does not confirm the new name, that the API returns no previous values, and that the change is irreversible without a prior read. This is exactly the destructive-mutation context the annotations cannot convey.

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?

Front-loads the core action and each sentence carries operational weight (irreversibility, verification workflow, identifier immutability). Slightly verbose, but nothing is 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 no explanation, yet the description adds the crucial caveat that the response does not confirm the new name. Combined with the irreversibility warning, an agent has everything needed to call this mutation 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 coverage is 100%, so the schema already documents both parameters, including the code's immutability and the lookup hint. The description reinforces that the code stays unchanged but adds no syntax or format detail beyond the schema, 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 (überschreibt) and the exact resource scoped (die Bezeichnung einer Kostenstelle), and clarifies that the code/identifier itself is not changed. This lets an agent distinguish it from bb_cost_locations_create/delete/search 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 Guidelines4/5

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

Gives clear context ('Gedacht für eine berichtigte Bezeichnung') and names the sibling to use for verification (bb_cost_locations_search before and after). It stops short of an explicit when-not-to-use statement, but the intended scenario is unambiguous.

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

Deploy Server