Buchhaltungsbutler MCP

Receipts: get receipts

receipts_list

Read-onlyIdempotent

Fetch receipts for a customer account by inbound or outbound direction, date range, and payment status. Supports paging to retrieve all matching accounting records without modifying them.

Instructions

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

get receipts

Get receipts for a specified customer account. The response includes the number of returned rows and an array of receipts data.

Use to search receipts by direction, date range or payment status.

To fetch one known receipt, use receipts_get_by_id.

list_direction is required and selects inbound or outbound receipts. Supports limit and offset; observed rows counts only the returned page. Continue paging until empty, deduplicate IDs and check progress.

Endpoint: POST /receipts/get

Input Schema

Name	Required	Description
`limit`	No	A limit of returned data. If no limit is given, the default will be 500. Also the maximum limit is 500. If specified, the field will be validated.
`order`	No	Possible fields are: date amount invoicenumber (invoice_number) invoicingparty (counterparty) Allowed values are 'ASC' and 'DESC' Example: {"date": "ASC"} {"date": "ASC", "amount": "DESC"}
`offset`	No	The offset for paging returned data. If no offset is given, the default will be 0. If specified, the field will be validated.
`date_to`	No	The receipt's issuing date in format 'YYYY-MM-DD' (e.g. '2017-04-26'). All receipts with issuing date including and before given value will be returned. If specified, the field will be validated. An empty string is not considered a valid date.
`deleted`	No	If true, only deleted receipts will be returned. If specified, the field will be validated.
`due_date`	No	The receipt's issuing due date in format 'YYYY-MM-DD' (e.g. '2017-04-26'). All receipts with the same due date given value will be returned. If specified, the field will be validated. An empty string is not considered a valid due date.
`date_from`	No	The receipt's issuing date in format 'YYYY-MM-DD' (e.g. '2017-04-26'). All receipts with issuing date including and after given value will be returned. If specified, the field will be validated. An empty string is not considered a valid date.
`counterparty`	No	The counterparty of the receipt, i.e. the invoicing party for type 'inbound' or the recipient for type 'outbound' (e.g. 'Peter Maier'). If specified, the field will be validated.
`invoicenumber`	No	The invoicenumber for the invoice. If specified, the receipts with the same invoicenumber will be retrieved.
`include_offers`	No	If true, offers will be included. If specified, the field will be validated.
`list_direction`	Yes	Can be either 'inbound' ("Eingangsbelege") or 'outbound' ("Ausgangsbelege").
`payment_status`	No	Can be either 'paid' ("bezahlt") or 'unpaid' ("unbezahlt"). If specified, the field will be validated.
`date_since_last_modified`	No	A date and time in format 'YYYY-MM-DD HH:MM:SS' (e.g. '2017-04-26 13:45:00'). If only 'YYYY-MM-DD' is specified, the time defaults to '23:59:59'. All receipts whose date_updated value is later than the specified value will be returned. If specified, the field will be validated. An empty string is not considered a valid date.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.1.5Nov 1, 2026
- changedOutput schema / properties / data / items / properties / counterparty / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / date_delivery / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / date_uploaded / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / deleted / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- 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"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / type / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
Changed15 schema fields changedv1.1.3Sep 26, 2026
- addedInput schema / properties / order / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / order / properties / amount
```
Added value: +{
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}
```
- addedInput schema / properties / order / properties / counterparty
```
Added value: +{
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}
```
- addedInput schema / properties / order / properties / date
```
Added value: +{
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}
```
- removedInput schema / properties / order / properties / field
```
Removed value: -{
-  "enum": [
-    "ASC",
-    "DESC"
-  ],
-  "type": "string"
-}
```
- addedInput schema / properties / order / properties / invoice_number
```
Added value: +{
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}
```
- addedInput schema / properties / order / properties / invoicenumber
```
Added value: +{
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}
```
- addedInput schema / properties / order / properties / invoicingparty
```
Added value: +{
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}
```
- removedInput schema / properties / order / required
```
Removed value: -[
-  "field"
-]
```
- changedOutput schema / properties / data / items / properties / account / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / amount / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / due_date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / invoicenumber / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / link_to_receipt_id_by_customer / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / payment_date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
Addedv1.1.2Sep 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The read-only banner largely restates annotations (readOnlyHint=true, destructiveHint=false), which earns no credit, but the description adds genuinely new behavior: the pagination contract ("observed `rows` counts only the returned page", "Continue paging until empty, deduplicate IDs and check progress"). That paging/dedup guidance is the highest-value content here since a naive caller would stop after one page. It stops short of describing ordering defaults or error behavior.

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 purpose, then usage, then the sibling alternative, then the paging caveat — a sensible order. It loses a little to redundancy: the emoji read-only banner and the repeated "**get receipts**" line duplicate annotation/title content, and "Endpoint: POST /receipts/get" is transport detail an MCP caller cannot act on.

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 13 parameters, an output schema and full annotation coverage, the description covers what it must: what is returned in shape terms, required vs optional intent, and paging behavior. The return-value sentence is redundant given the output schema, and no default ordering or empty-result behavior is mentioned, but nothing needed to call it correctly is missing.

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% and every parameter carries its own docstring, including formats and validation notes, so the schema does the heavy lifting. The description only adds the frequency of use framing around direction, date range and payment status — a useful filter summary, but it introduces no format or edge-case detail beyond the schema. Baseline 3 applies.

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 receipts") plus the scoping constraint ("for a specified customer account"), and explicitly names the sibling it is not (receipts_get_by_id). An agent can separate this from receipts_list_assigned_transactions or transactions_list without opening a 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 concrete selection criteria ("search receipts by direction, date range or payment status") and an explicit alternative with its triggering condition ("To fetch one known receipt, use receipts_get_by_id"). It also states that list_direction is required, which is the gating decision for calling this tool at all.

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

Deploy Server