BuchhaltungsButler MCP-Server

Overview Schema Source Related Servers Discussions Admin

BWA abholen

bb_reports_get_bwa

Read-onlyIdempotent

Retrieves a previously generated business analysis (BWA) report from BuchhaltungsButler, optionally with CSV and PDF files. Requires prior creation via bb_reports_create_bwa.

Instructions

Holt eine zuvor in BuchhaltungsButler erzeugte Betriebswirtschaftliche Auswertung ab, auf Wunsch samt Dateien. Vorbedingung ist ein Lauf von bb_reports_create_bwa; 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. error_code 8 heißt: Erzeugung läuft noch, einige Sekunden warten. 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 und pdf mit; ohne Angabe fehlt das Objekt files ganz. bb_reports_create_bwa kennt keinen Parameter, Dateien anzufordern; dass beide deshalb immer null bleiben, ist nicht verifiziert.
`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_bwa 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.9/5.0

Behavior5/5

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

Annotations already declare the safe read profile (readOnly/idempotent/non-destructive), and the description goes further with behavioral facts annotations cannot carry: the read-only-mode workflow constraint and the meaning of error_code 8 (transient, retry) and error_code 7 (permanent, no report). This is exactly the kind of runtime behavior an agent needs before invoking.

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?

Front-loaded with the core action, then preconditions, then error semantics — every sentence carries distinct, necessary information and nothing is repeated from the schema. Dense but zero waste.

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 retrieval tool with an output schema (so return values need not be explained) and full schema coverage, the description still supplies the missing pieces: the creation precondition, the read-only fallback, and the two error codes. Nothing needed to call it correctly is absent.

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 the baseline is 3, and the schema already documents get_files, response_format, and report_id_by_customer richly. The description adds a cross-tool semantic not present in the schema: that report_id_by_customer is the id_by_customer returned by bb_reports_create_bwa, which clarifies the provenance of the required value.

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 (retrieves/fetches) and resource (a previously created BWA, optionally with files), and explicitly names the sibling that creates the input (bb_reports_create_bwa) and the alternative under read-only mode (bb_reports_get_ledger). An agent can distinguish this retrieval tool from its creation counterpart and its sibling report tool 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 precondition (bb_reports_create_bwa must have run), tells the agent which value to pass (its id_by_customer), and names the fallback when BB_MCP_READ_ONLY is active (only bb_reports_get_ledger). It also routes on error codes (8 = still running, wait; 7 = no report), so retry vs. abort decisions are fully specified.

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

Deploy Server