Skip to main content
Glama
Buchhaltungsbutler MCP

Buchhaltungsbutler MCP

Receipts: delete receipt by id_by_customer

receipts_delete
DestructiveIdempotent

Delete a mistakenly filed receipt by per-customer ID to remove it from the customer account. The deletion is recoverable with receipts_restore.

Instructions

🔴 DESTRUCTIVE · deletes data: Deletes or cancels a record. Confirm with the user before calling. Receipt deletes are restorable; cost-location deletes are not. Cancelling a posting deletes it if it is not yet fixed, otherwise it books a reversal posting.

delete receipt by id_by_customer

Mark a receipt as deleted for a specified customer account by id_by_customer. You can get the "id_by_customer" by using the "/receipts/get method" first.

Use to remove a receipt that was filed by mistake.

Recoverable: receipts_restore brings the receipt back. Confirm with the user before calling.

Endpoint: POST /receipts/delete/id_by_customer

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id_by_customer": "<id_by_customer>"
    },
    "name": "receipts_delete"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
messageNoblank
successYesSuccess boolean
id_by_customerNoblank

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=true and openWorldHint=true, but the description adds genuinely non-structured facts: receipt deletes are restorable while cost-location deletes are not, and confirmation is required before calling. The opening paragraph mixes in cost-location and posting-cancellation semantics that don't apply to this endpoint, which dilutes the otherwise strong disclosure.

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 destructive warning and confirmation prompt are correctly front-loaded, but the generic preamble ('Deletes or cancels a record ... cost-location deletes are not ... Cancelling a posting deletes it if it is not yet fixed') is boilerplate for other tools and is noise here. The endpoint line at the bottom adds little for an agent that already has the tool bound.

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 and a single fully-described parameter, the description only needs the operational context it does supply: destructiveness, restorability, confirmation requirement, and ID provenance. The one gap is the ambiguous pointer to where id_by_customer comes from.

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% and the parameter is documented there, so baseline is 3. The description adds a provenance hint ('/receipts/get method') but that conflicts slightly with the schema's wording ('obtained from the corresponding list tool'), leaving the agent unsure whether receipts_get_by_id or receipts_list supplies the value.

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 ('Mark a receipt as deleted ... by id_by_customer') and scopes it to a single customer account. It also names the inverse sibling, receipts_restore, so an agent can tell this apart from restore/list/get tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('remove a receipt that was filed by mistake'), a prerequisite for obtaining the id ('use the /receipts/get method first'), and a confirm-with-user instruction. It also points at receipts_restore as the recovery path, though it stops short of stating when an agent should prefer cancelling via postings_cancel instead.

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