Skip to main content
Glama

MaxRechnung

Zahlungseingang berichtigen

amend_payment
Destructive

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

Zahlungseingang berichtigen

Berichtigt Betrag, paid_on oder Notiz eines Zahlungseingangs – nur am Erfassungstag (deutsche Zeitzone) und nur solange nicht storniert. Danach 409; dann stornieren und neu erfassen. Ein Skonto-Ausgleich (kind: skonto) wird nicht berichtigt, nur storniert (409). Die Berichtigung wird als payment_edited protokolliert.

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": "amend_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPfad-Parameter id
bodyNoJSON-Request-Body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Well beyond the annotations: it discloses the plan gate and its error response, the 409 failure mode and its cause, the immutability of cancelled and skonto payments, and the payment_edited audit trail. The destructiveHint=true is consistent with the described mutation, though it does not say whether the edit is reversible or what the response body contains.

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-loads the tier requirement and keeps the constraint, failure mode, and fallback in a tight block with no filler. Minor waste in restating the tool name as a heading and repeating the 409 consequence twice.

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

Completeness5/5

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

For a two-parameter mutation with a nested body and no output schema, the description covers access gating, allowed scope, error codes, the alternative workflow, and audit logging — everything needed to call it correctly or route elsewhere.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the real constraints on paid_on and amount (same-day, non-cancelled) that the schema cannot express. It does, however, omit `method` from the list of correctable fields even though the request body exposes it, which could mislead an agent into thinking method changes are rejected.

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+resource ('Zahlungseingang berichtigen') and enumerates the mutable fields (Betrag, paid_on, Notiz). It also scopes the operation in time and state (only on the entry day, only while not cancelled), which lets an agent separate it from cancel_payment and record_payment without opening the 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?

Explicit when-to-use and when-not-to-use: allowed only on the capture day in German timezone and only if the payment is not cancelled; otherwise the API returns 409 and the correct path is stornieren and re-record. The skonto case is called out as never correctable, only cancellable, and the Business-tier prerequisite with its plan_required error is stated upfront.

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