Buchhaltungsbutler MCP

Settings: get postingaccounts

postingaccounts_list

Read-onlyIdempotent

Retrieve chart of accounts to locate posting account numbers for transactions like office supplies before booking. Read-only; filter, page, or exclude debtors, creditors, and bank accounts as needed.

Instructions

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

get postingaccounts

Get all postingaccounts

Use to list the chart of accounts, for example to find the posting account number for office supplies before booking.

Not bank accounts. For the bank, cash and credit-card accounts transactions belong to, use accounts_list.

Supports limit and offset; a full SKR chart runs to several hundred rows. Do not assume rows is the grand total: continue paging until empty and check progress, or filter instead. v1 offers no delete endpoint for posting accounts.

Endpoint: POST /settings/get/postingaccounts

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	limit of the results, default is 1000 results. If specified, the field will be validated.
`order`	No	the order of the results.The following options are valid:postingaccount_number ASC \| DESCname ASC \| DESCtype ASC \| DESC. If specified, the field will be validated.
`offset`	No	offset of the results, default is 0. If specified, the field will be validated.
`exclude_debtors`	No	exclude all debtor postingaccounts from result. If specified, the field will be validated.
`exclude_accounts`	No	exclude all base accounts (e.g. bank accounts) from result. If specified, the field will be validated.
`exclude_creditors`	No	exclude all creditor postingaccounts from result. If specified, the field will be validated.
`exclude_postingaccounts`	No	exclude all postingaccounts from result. If specified, the field will be validated.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	An array of postingaccounts data
`rows`	No	Number of returned rows
`message`	No	blank
`success`	Yes	Success boolean

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.3Sep 26, 2026
- changedOutput schema / properties / data / items / properties / parent_name / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / subtype / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
Addedv1.1.2Sep 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover readOnly and non-destructive hints, but the description adds crucial behavioral details: supports limit/offset, the full SKR chart is large, 'rows' is not the grand total, and to continue paging or filter. These go beyond annotations and are essential for correct usage.

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 and front-loads the purpose, but includes some tangential notes like 'v1 offers no delete endpoint for posting accounts' that, while informative, are not needed to invoke this tool. Slightly longer than necessary but each part has purpose.

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 covers purpose, usage, pagination behavior, and sibling differentiation. With an output schema present and annotations covering safety, nothing essential is missing. An agent has all needed information to call it correctly.

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% with descriptions for all 7 parameters, so the baseline is 3. The description adds value by explaining limit/offset in context (large dataset, pagination advice) and suggests filtering as an alternative, enhancing understanding of those parameters, though it doesn't elaborate on the exclude_* flags.

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 fetches posting accounts (chart of accounts) with 'Get all postingaccounts' and explains its use case (finding posting account numbers). It explicitly differentiates from accounts_list by stating 'Not bank accounts', so an agent can distinguish it from siblings without opening schemas.

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 gives explicit when-to-use context ('Use to list the chart of accounts, for example to find the posting account number for office supplies before booking') and when-not-to-use by directing to accounts_list for bank accounts. It also mentions pagination and filtering as alternatives, leaving no ambiguity about selection.

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

Deploy Server