BuchhaltungsButler MCP-Server

unassign_receipt_from_transaction

Removes the link between a receipt and a transaction using their customer-specific IDs.

Instructions

Entfernt die Zuordnung eines Belegs von einer Banktransaktion.

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": {
      "transaction_id_by_customer": "<transaction_id_by_customer>",
      "receipt_id_by_customer": "<receipt_id_by_customer>"
    },
    "name": "unassign_receipt_from_transaction"
  }
}

Input Schema

Name	Required	Description
`api_key`	No	API-Key des zu verwaltenden Kunden. Optional, falls BUCHHALTUNGSBUTLER_API_KEY als Umgebungsvariable gesetzt ist.
`receipt_id_by_customer`	Yes	Die id_by_customer des Belegs.
`transaction_id_by_customer`	Yes	Die id_by_customer der Transaktion.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 21, 2026

TDQS

C2.8/5.0

Behavior1/5

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

There are no annotations, and the description does not disclose any side effects, permissions, reversibility, or other behavioral aspects. It only states the action without describing what happens beyond the removal.

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

Conciseness5/5

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

The description is a single, clear sentence with no unnecessary words. It is concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description does not mention what happens after the action (e.g., return value, confirmation) and no output schema is provided. It could be more complete by explaining the expected result or any side effects, making it somewhat incomplete for a simple action.

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?

The description adds no additional meaning to the parameters beyond the schema descriptions, which already provide 100% coverage (e.g., 'Die id_by_customer des Belegs'). Since schema coverage is high, a baseline of 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 clearly states the action: 'Entfernt die Zuordnung eines Belegs von einer Banktransaktion' (removes the assignment of a receipt from a bank transaction). It uses a specific verb and specifies the resource, making it distinct from sibling tools like assign_receipt_to_transaction.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or conditions. The description only states the action without contextual usage instructions.

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