Skip to main content
Glama
Sign In
Buchhaltungsbutler MCP

Buchhaltungsbutler MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Transactions: get all receipts assigned to a specific transaction

transactions_list_assigned_receipts
Read-onlyIdempotent

Fetches all receipts assigned to a specific transaction so you can verify which documents, such as invoices, are linked to a payment.

Instructions

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

get all receipts assigned to a specific transaction

Get all receipts assigned to a specific transaction for a specified customer account by id_by_customer. You can get the "id_by_customer" by using the "/transactions/get method" first.

Use to see which receipts are linked to a given bank transaction, for example to check whether a payment has its invoice attached.

For the opposite direction, use receipts_list_assigned_transactions.

Endpoint: POST /transactions/assigned-receipts/get

Input Schema

NameRequiredDescriptionDefault
confirmed_onlyNoIf true, only confirmed assignments will be returned. If specified, the field will be validated.
transaction_id_by_customerYesThe id_by_customer of the transaction.

Output Schema

NameRequiredDescriptionDefault
dataNoAn array of receipts data
rowsNoNumber of returned rows
messageNoblank
successYesSuccess boolean

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.5
    • changedOutput schema / properties / data / items / properties / filename / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / data / items / properties / id_by_customer / type
      Previous value: -[
-  "string",
-  "integer"
-]New value: +[
+  "string",
+  "integer",
+  "null"
+]
  2. Changed1 schema field changedv1.1.3
    • changedOutput schema / properties / data / items / properties / id_by_customer / type
      Previous value: -"string"New value: +[
+  "string",
+  "integer"
+]
  3. Addedv1.1.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is largely pre-supplied; the emoji banner restates it. The description still adds genuine context: the endpoint and the fact that id_by_customer must be derived from another call first. It does not cover pagination or result-size behavior, keeping it just short of a 5.

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?

Purpose is front-loaded and the body is two short paragraphs plus an endpoint line. The emoji read-only banner and the bolded title duplicate the title field and annotations, costing a little space for no new information.

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 rich annotations and an output schema, the description only needs to establish purpose, direction, and how to obtain the id — all present. Minor gaps remain around ordering/pagination of the returned receipt list, but nothing that would cause a mis-invocation.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning the schema cannot: where the required `transaction_id_by_customer` value comes from (the /transactions/get method). The optional `confirmed_only` flag is only explained by the schema, which is acceptable given full coverage.

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?

States a specific verb and resource ('get all receipts assigned to a specific transaction') and explicitly scopes it to one transaction identified by id_by_customer. It also names the inverse sibling, `receipts_list_assigned_transactions`, so the agent can distinguish the two directions 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?

Gives an explicit use case ('to check whether a payment has its invoice attached'), a prerequisite ('you can get the id_by_customer by using the /transactions/get method first'), and an alternative for the opposite direction. Nothing about when to pick this tool is left to inference.

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