BuchhaltungsButler MCP-Server

Overview Schema Source Related Servers Discussions Admin

Summen- und Saldenliste abholen

bb_reports_get_sums

Read-onlyIdempotent

Retrieve a previously created sums and balances report from BuchhaltungsButler, optionally with its files. Use the report_id_by_customer from bb_reports_create_sums; balances are keyed by account.

Instructions

Holt eine zuvor in BuchhaltungsButler erzeugte Summen- und Saldenliste ab, auf Wunsch samt Dateien. Vorbedingung ist ein Lauf von bb_reports_create_sums; dessen id_by_customer ist hier einzusetzen. Bei aktivem BB_MCP_READ_ONLY ist dieser erste Schritt gesperrt, dann liefert nur bb_reports_get_ledger eine Auswertung. Die Salden stehen im Objekt sums, geschlüsselt nach Kontonummer. error_code 8 heißt: Erzeugung läuft noch. error_code 7 heißt: kein Bericht zu dieser Kennung.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`get_files`	No	true liefert die Dateien base64-kodiert unter csv, pdf und csv_archive mit. Geliefert wird nur, was bb_reports_create_sums angefordert hat, alles andere ist null. Ohne Angabe fehlt das Objekt files ganz.
`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
`report_id_by_customer`	Yes	Kennung der zuvor mit bb_reports_create_sums erzeugten Auswertung, deren id_by_customer. In Suchergebnissen erscheint sie als String; hier ohne Anführungszeichen übergeben. Ohne Bericht dazu antwortet die API mit error_code 7.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false). The description adds valuable behavioral context: the prerequisite creation step, the read-only mode restriction, the structure of the sums object, and the meaning of error codes 7 and 8. It does not detail rate limits or pagination, but with annotations covering the safety profile, this is strong.

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?

The description is a few sentences, front-loaded with the core purpose, then prerequisites, then error codes. It is efficient and every sentence adds value, though it could be slightly more concise by combining some error code details.

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?

Given the tool has an output schema and rich annotations, the description covers all necessary context: prerequisite tool, read-only mode behavior, structure of sums, and error codes. It fully equips an agent to invoke correctly and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description goes beyond the schema by explaining that report_id_by_customer is the id_by_customer from bb_reports_create_sums, and that error_code 7 occurs if no report exists. It also mentions 'auf Wunsch samt Dateien' which corresponds to get_files, though the schema already details that parameter. The description adds meaning for the required parameter and error conditions, raising it to 4.

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+resource: 'Holt eine zuvor in BuchhaltungsButler erzeugte Summen- und Saldenliste ab, auf Wunsch samt Dateien'. It clearly distinguishes itself from siblings by naming the prerequisite tool bb_reports_create_sums and the alternative bb_reports_get_ledger.

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?

Explicitly says when to use it: after running bb_reports_create_sums, and provides the condition for an alternative ('Bei aktivem BB_MCP_READ_ONLY ... dann liefert nur bb_reports_get_ledger eine Auswertung'). It also explains what error codes mean, guiding the agent on next steps.

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

Deploy Server