BuchhaltungsButler MCP-Server

Overview Schema Source Related Servers Discussions Admin

Kontenblatt abrufen

bb_reports_get_ledger

Read-onlyIdempotent

Retrieve a ledger sheet for a posting account within a date range, including postings and running balance. No generation step required, so it works even in read-only mode.

Instructions

Liefert das Kontenblatt eines Sachkontos aus BuchhaltungsButler für einen Zeitraum, also dessen Buchungen mit laufendem Saldo. Anders als bb_reports_get_bwa und bb_reports_get_sums braucht es keinen Erzeugungsschritt und bleibt auch bei aktivem BB_MCP_READ_ONLY nutzbar. Weder limit noch offset: Ein stark bebuchtes Konto liefert alles auf einmal, lange Zeiträume also in Monatsfenster zerlegen. Ein leeres Kontenblatt ist kein Fehler, sondern ein Konto ohne Buchung.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`base`	No	Datum der Periodenzuordnung: 'date' Buchungsdatum, 'date_delivery_else_date' Leistungsdatum und ersatzweise Buchungsdatum. Ohne Angabe 'date'. Mit dem zweiten Wert können Buchungen außerhalb des Rechnungsdatums erscheinen; nicht verifiziert.
`date_to`	Yes	Letzter Tag des Zeitraums als YYYY-MM-DD, zum Beispiel 2026-03-31. Ein leerer String wird abgelehnt; das Feld stattdessen weglassen. Der Zeitraum schließt diesen Tag ein.
`date_from`	Yes	Erster Tag des Zeitraums als YYYY-MM-DD, zum Beispiel 2026-01-01. Ein leerer String wird abgelehnt; das Feld stattdessen weglassen. Der Zeitraum schließt diesen Tag ein.
`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
`postingaccount_number`	Yes	Nummer des Sachkontos, dessen Kontenblatt geliefert wird, zum Beispiel 4920, als ganze Zahl ohne Anführungszeichen. Nachschlagen mit bb_postingaccounts_search. Zu einem Konto, das es nicht gibt, antwortet die API mit error_code 16.

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"
+        ]
+      },
+      "balanceAfterSide": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "costLocationName": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "cost_location": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "counterRecordPostingaccountNumber": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "date": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id_by_customer": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "journal_number": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "postingTextFull": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "receiptsAssignedFileSuffix": {
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "receiptsAssignedFilenamesServerPlain": {
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "receipts_direction": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "receipts_id_by_customer": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "record_amount": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "record_amount_cents": {
+        "type": "integer"
+      },
+      "record_side": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "reversal_for_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "reversed_by_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "standard_chart": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "tax_journal_number": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "tax_key": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "tax_key_effective": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "transactions_id_by_customer": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "vatPostingaccountNumbers": {
+        "type": [
+          "array",
+          "null"
+        ]
+      },
+      "vatRate": {
+        "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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable behavior beyond these: no limit/offset, so heavily booked accounts return everything at once, and an empty ledger is not an error but an account without postings. It also reinforces read-only compatibility, which aligns with annotations.

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?

The description is a single paragraph of four sentences, all relevant and front-loaded with the primary purpose. It efficiently covers differentiation, pagination caveat, and error interpretation without fluff. Every sentence earns its place.

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?

The description is complete for a filtered-list tool. It covers purpose, usage guidance, behavioral caveats (no pagination, empty result handling), and works with read-only mode. An output schema exists, so return values are covered. The schema descriptions handle parameter details and error codes, leaving nothing essential missing.

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 baseline is 3. The description does not add parameter-specific meaning beyond what the schema provides; it only mentions the absence of limit/offset, which is a tool-level behavior rather than parameter semantics. The schema already documents each parameter thoroughly.

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 clearly states the tool returns the ledger (Kontenblatt) of a posting account for a period, with running balances. It explicitly distinguishes itself from sibling tools bb_reports_get_bwa and bb_reports_get_sums by noting it requires no generation step, making its purpose unambiguous.

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?

The description provides clear usage context by comparing with alternatives: unlike bb_reports_get_bwa and bb_reports_get_sums, it does not need a generation step and works in read-only mode. It also advises splitting long periods into monthly windows due to lack of pagination. However, it does not explicitly state when to choose this over those siblings beyond the generation difference.

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

Deploy Server