Buchhaltungsbutler MCP

Receipts: get receipts

receipts_list

Read-onlyIdempotent

Search and retrieve receipts for a customer account by direction, date range, payment status, or invoice number. Filter, sort, and paginate results to locate matching inbound or outbound documents.

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; the response reports the total in rows.

Endpoint: POST /receipts/get

Input Schema

TableJSON 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

TableJSON 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.

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?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description reinforces but doesn't contradict. It adds useful behavioral context: the response includes row count and array, the requirement of list_direction, and the POST endpoint. No contradictions found.

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 front-loaded with a read-only note, then explains the purpose and usage. It's reasonably concise, though it includes some redundancy (repeating 'get receipts' and the endpoint). Still, every sentence contributes value.

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?

For a tool with 13 parameters and nested objects, the description covers the main use cases and points to the correct sibling. Since an output schema exists, the description doesn't need to detail return values. It's adequately complete.

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 coverage is 100%, so the schema documents all parameters thoroughly. The description adds a little extra by noting list_direction is required and that limit/offset are supported, but it doesn't go beyond the schema in any substantial way. Baseline 3 is appropriate.

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 ('get receipts') and resource, and clarifies it fetches receipt data for a customer account. It explicitly differentiates from receipts_get_by_id, so an agent can tell them apart.

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 clearly states when to use this tool (search by direction, date range, or payment status) and explicitly names the alternative (receipts_get_by_id) for fetching a single known receipt. This provides strong routing guidance.

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

Deploy Server