Skip to main content
Glama
ohneben

Buchhaltungsbutler MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Transactions: get transaction by id_by_customer

transactions_get_by_id
Read-onlyIdempotent

Retrieve a single bank transaction by its per-customer ID. Use when you have the ID from the transactions list to fetch exact transaction details.

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

TableJSON Schema
NameRequiredDescriptionDefault
id_by_customerYesRequired per-customer record ID obtained from the corresponding list tool.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoAn array of transaction data
messageNoblank
successYesSuccess boolean

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.3
    • 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"
+]
  2. Addedv1.1.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description reinforces safety with 'READ-ONLY' and 'Makes no changes', and adds meaningful behavioral detail beyond annotations: the response contains an array, and id_by_customer is a per-customer UI counter rather than a global database id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the READ-ONLY note and contains useful routing information, but it includes some redundancy: the bolded heading repeats the tool name/title, and 'Get a single transaction...' appears twice in slightly different forms. It is not overly long, but a few sentences could be tightened.

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?

For a one-parameter read-only tool with an output schema and clear annotations, the description covers everything needed: what to fetch, where the id comes from, the alternative list tool, the response shape, and the exact endpoint. No essential operational context 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%, so the schema already documents the only parameter. The description adds value by explaining that id_by_customer is the per-customer counter shown in the UI and not a global database id, clarifying an ambiguity the schema alone does not fully resolve.

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 action ('Get a single transaction'), the resource ('for a specified customer account by id_by_customer'), and the distinguishing scope ('single bank transaction whose id you already have'). It also explicitly contrasts itself with transactions_list, making the tool's specific role unambiguous.

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 direct usage context: use it when you already have the id_by_customer, and use transactions_list 'to search or page through transactions'. It also explains how to obtain the id_by_customer in the first place, which is actionable guidance.

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