Skip to main content
Glama
ohneben

Buchhaltungsbutler MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Reports: get sums report postingaccount ledger

reports_get_sums_ledger
Read-onlyIdempotent

Retrieve the postingaccount ledger for a selected account and date range. Get on-demand postings without pre-creating a sums report.

Instructions

🟢 READ-ONLY: Fetches data. Makes no changes to the accounting records.

get sums report postingaccount ledger

Returns the postingaccount ledger ("Kontenblatt") of one postingaccount, holding its postings of the requested period.

The postingaccount numbers available for a sums report are provided by reports/get/sums, both as the keys of the 'sums' object and as its entries' 'postingaccount_number'.

In contrast to the report itself the ledger is created on the fly, so no report has to be created beforehand. Note that retrieving the ledger of a postingaccount holding a lot of postings may take a while.

Use to read one posting account's ledger for a bounded date range.

For the totals across all posting accounts, use reports_get_sums.

The API returns the ledger on demand; no previously generated sums report or report ID is required.

Endpoint: POST /reports/get/sums/ledger

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseNoThe date the postings are taken into account by. Can be either 'date' ("Buchungsdatum") or 'date_delivery_else_date' ("Buchungs- und Leistungsdatum"). If specified, the field will be validated.
date_toYesThe last day of the period the ledger is returned for, in format 'YYYY-MM-DD' (e.g. '2026-03-31').
date_fromYesThe first day of the period the ledger is returned for, in format 'YYYY-MM-DD' (e.g. '2026-01-01').
postingaccount_numberYesThe number of the postingaccount to return the ledger for

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNoblank
successYesSuccess boolean
report_sums_postingaccount_ledgerNoThe ledger's data, containing the keys 'integrityError', 'postingaccount_number' and 'postingaccountLedger'. The 'postingaccount_number' is the number of the postingaccount the ledger has been returned for, whereas 'postingaccountLedger' is an array of the postingaccount's postings within the requested period, each one providing its date, posting text, counter postingaccount, amount, vat and the unformatted balance 'balanceAfterAbsolute' together with its side 'balanceAfterSide'. The array is empty if there are no postings in the requested period.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "message": {
+      "description": "blank",
+      "type": "string"
+    },
+    "report_sums_postingaccount_ledger": {
+      "description": "The ledger's data, containing the keys 'integrityError', 'postingaccount_number' and 'postingaccountLedger'.\n\nThe 'postingaccount_number' is the number of the postingaccount the ledger has been returned for, whereas 'postingaccountLedger' is an array of the postingaccount's postings within the requested period, each one providing its date, posting text, counter postingaccount, amount, vat and the unformatted balance 'balanceAfterAbsolute' together with its side 'balanceAfterSide'. The array is empty if there are no postings in the requested period.",
+      "type": "object"
+    },
+    "success": {
+      "description": "Success boolean",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changedv1.1.0
    • removedInput schema / properties / api_key
      Removed value: -{
-  "description": "Optional. The BB customer api_key to act on. Defaults to the BB_API_KEY configured on the server — only set this to target a different customer.",
-  "type": "string"
-}
  3. Addedv1.0.2

TDQS

A4.3/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 valuable behavioral context: the ledger is created on the fly, no report must be created beforehand, and retrieving a ledger with many postings may take a while. This goes beyond the annotations and helps set expectations.

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 well-structured with a clear READ-ONLY banner, a concise summary, and useful context. It is slightly longer than strictly necessary, with some repetition (e.g., 'no report has to be created beforehand' and 'no previously generated sums report or report ID is required'), but the information is front-loaded and each section earns its place.

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?

The description is complete for a read-only ledger tool: it states the resource, the period, the source of valid account numbers, the on-the-fly behavior, and the performance caveat. An output schema exists, so return values need not be described. The only minor gap is that it doesn't explicitly mention the endpoint format beyond the URL, but that is not essential for an agent to invoke the tool correctly.

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 schema already documents all four parameters. The description adds context about how to find valid postingaccount numbers (via reports/get/sums) and clarifies the date range semantics, but it does not add much detail beyond the schema for individual parameters. Baseline 3 is appropriate.

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 postingaccount ledger ('Kontenblatt') for one postingaccount within a requested period, using a specific verb ('Returns') and resource. It distinguishes itself from the related reports_get_sums tool by explicitly noting it reads one account's ledger rather than totals across all accounts.

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 explicitly says when to use this tool ('Use to read one posting account's ledger for a bounded date range') and when not to ('For the totals across all posting accounts, use reports_get_sums'). It also clarifies that no previously generated report is required, which prevents an agent from unnecessarily creating a report first.

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

Deploy Server

Other Tools