Buchhaltungsbutler MCP

Transactions: get transaction by id_by_customer

transactions_get_by_id

Read-onlyIdempotent

Fetch a single bank transaction by its per-customer ID to retrieve detailed record data without searching. Use when you already have the ID from a list result.

Instructions

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

get transaction by id_by_customer

Get a single transaction for a specified customer account by id_by_customer. You can get the "id_by_customer" by using the "/transactions/get method" first. The response includes an array of transaction data.

Use to fetch a single bank transaction whose id you already have.

To search or page through transactions, use transactions_list.

id_by_customer is the per-customer counter shown in the BuchhaltungsButler UI, not a global database id.

Endpoint: POST /transactions/get/id_by_customer

Input Schema

Name	Required	Description	Default
`id_by_customer`	Yes	Required per-customer record ID obtained from the corresponding list tool.

Output Schema

Name	Required	Description
`data`	No	An array of transaction data
`message`	No	blank
`success`	Yes	Success boolean

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv1.1.5Nov 1, 2026
- changedOutput schema / properties / data / properties / account / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / account_number / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / amount / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / bank_code / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / booking_date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / currency / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / id_by_customer / type
```
Previous value: -[
-  "string",
-  "integer"
-]New value: +[
+  "string",
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / purpose / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / to_from / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / value_date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed6 schema fields changedv1.1.3Sep 26, 2026

addedInput schema / properties / id_by_customer

Added value: +{
+  "description": "Required per-customer record ID obtained from the corresponding list tool.",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / required
```
Added value: +[
+  "id_by_customer"
+]
```
changedOutput schema / properties / data / properties / bank_name / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
changedOutput schema / properties / data / properties / booking_text / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
changedOutput schema / properties / data / properties / id_by_customer / type
```
Previous value: -"string"New value: +[
+  "string",
+  "integer"
+]
```

changedOutput schema / properties / data / properties / type / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

Addedv1.1.2Sep 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the leading '🟢 READ-ONLY' sentence is largely redundant. The description does add genuine non-annotated context: the id is a per-customer counter visible in the BuchhaltungsButler UI rather than a global database id, and it discloses the underlying endpoint POST /transactions/get/id_by_customer.

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?

Front-loaded with the operation, then usage, then the id caveat, then the endpoint — a sensible order. It loses a little to the bolded restatement of the title and the annotation-repeating READ-ONLY banner.

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?

With an output schema present, the description needn't explain return values, and the one-parameter read tool is otherwise fully specified. The only loose end is the slight inconsistency about where the id comes from (a 'get method' vs. the list tool).

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, but the description goes beyond the schema by explaining what id_by_customer actually is (a per-customer counter from the UI, not a global id) and where to get it. There is a minor mismatch in that the description points to '/transactions/get' while the schema says 'corresponding list tool'.

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 and resource ('Get a single transaction ... by id_by_customer') and explicitly contrasts itself with the sibling listing tool. An agent can distinguish it from transactions_list and receipts_get_by_id without opening either 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?

It gives an explicit positive case ('Use to fetch a single bank transaction whose id you already have'), an explicit redirect for the other case ('To search or page through transactions, use transactions_list'), and tells the agent how to obtain the required id first. Both when-to-use and the alternative are covered.

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

Deploy Server