Skip to main content
Glama

MaxRechnung

Zahlungseingang stornieren

cancel_payment
Destructive

Tarif: ab Business (darunter antwortet die API mit plan_required).

Zahlungseingang stornieren

Storniert den Zahlungseingang (setzt voided_at). Die Zeile bleibt in der Historie erhalten, zählt aber nicht mehr zum bezahlten Betrag; der Rechnungsstatus wird neu berechnet.

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": "<id>"
    },
    "name": "cancel_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPfad-Parameter id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description explains the soft-delete semantics: the row stays in history but no longer counts toward the paid amount, and the invoice status is recalculated as a side effect. It also discloses the plan_required failure mode, which an agent cannot get from the annotations.

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 plan requirement is front-loaded and the effect is described in tight sentences. The line 'Zahlungseingang stornieren' merely repeats the title and adds no information, a small but real redundancy.

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 single-parameter mutation tool with destructive annotations, the definition covers preconditions, mutation effect, and side effects well. With no output schema present, it leaves unstated what the call returns and whether a voided payment can be restored, which is a modest gap.

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?

There is a single required uuid parameter with 100% schema description coverage, so the schema does the heavy lifting. The description adds no meaning to the id (e.g., whether it is the payment id versus the invoice id), which matters given the sibling tools operate on invoices.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Storniert den Zahlungseingang') and specifies the mechanism ('setzt voided_at'), which makes it distinguishable from a payment amendment or an invoice cancellation. It stops short of naming a sibling or stating explicitly how it differs from cancel_invoice, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

A useful precondition is given: the tool requires the Business plan or higher, and the API otherwise answers with plan_required. There is no guidance on when to choose this over amend_payment or cancel_invoice, nor on any exclusions (e.g., already-voided rows), so usage is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources