BuchhaltungsButler MCP-Server

Overview Schema Source Related Servers Discussions Admin

Summen- und Saldenliste abholen

bb_reports_get_sums

Read-onlyIdempotent

Retrieve a previously generated sums and balances report by report ID. Returns account balances stored under 'sums', with optional base64 files, for use after report creation.

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
`items`	No
`message`	No
`success`	Yes
`summary`	No
`endpoint`	No
`rows_returned`	No
`_contract_warnings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.2Sep 16, 2026

removedOutput schema / properties / data

Removed value: -{
-  "type": [
-    "object",
-    "array",
-    "string",
-    "null"
-  ]
-}

addedOutput schema / properties / items

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "balanceAfterAbsolute": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "balanceAfterCredit": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "balanceAfterDebit": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "balanceAfterSide": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "balanceBeforeAbsolute": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "balanceBeforeCredit": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "balanceBeforeDebit": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "balanceBeforeSide": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "class": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "postingaccount": {
+        "type": "string"
+      },
+      "postingaccount_number": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "sumPeriodCredit": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "sumPeriodDebit": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "type": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / rows_returned
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / summary

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: it documents error_code 8 (generation still running), error_code 7 (no report for this id), the sums object structure keyed by account number, and the read-only mode interaction. This is meaningful behavioral context the annotations don't provide.

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?

Five sentences, each earning its place: purpose, prerequisite, read-only alternative, return structure, and error codes. It's dense but not padded. Slightly more structure could improve scannability, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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. The tool is moderately complex — it has a prerequisite, an error-state protocol, a read-only mode interaction, and a sibling alternative — and all of these are covered. Nothing an agent needs to call it correctly is missing.

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% and each parameter is well-documented in the schema. The description adds one genuinely useful nuance: the id_by_customer appears as a string in search results but must be passed without quotes here — a common agent failure point. This goes beyond the schema's own description.

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?

The description states a specific verb+resource ('Holt eine zuvor erzeugte Summen- und Saldenliste ab') and distinguishes itself from siblings by naming its predecessor (bb_reports_create_sums) and its alternative (bb_reports_get_ledger). An agent can immediately tell this tool fetches a pre-generated trial balance rather than generating one.

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?

The description is explicit about the prerequisite (must run bb_reports_create_sums first and pass its id_by_customer), and names the exact alternative (bb_reports_get_ledger) to use when BB_MCP_READ_ONLY blocks the creation step. This gives an agent clear when-to-use and when-not-to-use guidance.

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

Deploy Server