Skip to main content
Glama

MaxRechnung

Zahlungseingang erfassen

record_payment

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

Zahlungseingang erfassen

Erfasst eine (Teil-)Zahlung zu invoice_id: einer Rechnung oder einer Korrektur mit positivem Betrag (Nachberechnung, Grenze ist ihr eigener Betrag). Der Status wird abgeleitet: sent → partial → paid. Ein negativer Betrag ist eine Rückzahlung, höchstens bis zur erhaltenen Summe (sonst 409); zu einer Minus-Korrektur lässt sich nur die Erstattung an den Kunden erfassen. Übersteigt der Betrag den offenen Rest (Rechnungsbetrag nach Minus-Korrekturen minus erfasste Zahlungen), entscheidet overpayment wie der Zahlungsdialog der App: credit erfasst den vollen Betrag und weist das Guthaben aus (amount_open der Rechnung wird negativ, die Zahlung trägt overpayment: true), ignore erfasst nur den offenen Rest und vermerkt den Mehrbetrag in note. Ohne overpayment lehnt die API eine Überzahlung mit 422 ab (Feldfehler an amount und overpayment); ist bei ignore nichts mehr offen, 409. Kommt eine gleichzeitige Zahlung dazwischen, lehnt die Datenbank ab (409). Eine stornierte Rechnung (void) nimmt nur noch Rückzahlungen bis zur erhaltenen Summe an, sonst 409; der Status bleibt void. kind: skonto gleicht den offenen Rest als Skonto aus, ohne amount und note: nur bei einer Rechnung mit Skonto in den Zahlungsbedingungen, Status sent oder partial, und höchstens bis zum Skonto-Abzug (sonst 409). Die Rechnung steht dann auf paid; der DATEV-Stapel bucht den Rest auf „Gewährte Skonti“ statt auf die Bank. Business-Tarif.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "record_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON-Request-Body.
_idempotency_keyNoOptional. Geht als Header `Idempotency-Key` an die API: derselbe Wert mit demselben Aufruf liefert 24 Stunden lang die erste Antwort zurück, statt den Vorgang zu wiederholen. Bei einem Wiederholversuch denselben Wert schicken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false, so the description carries the rest and does so thoroughly: Business plan prerequisite (`plan_required`), derived status chain `sent`→`partial`→`paid`, `overpayment: credit/ignore` effects on `amount_open`, 409/422 failure modes including concurrent-payment DB rejection, and DATEV posting to 'Gewährte Skonti' for skonto. That is substantial behavior beyond what the annotations disclose.

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 plan prerequisite is front-loaded, but the body is a single dense paragraph that packs status transitions, error codes and DATEV behavior into prose, and the repeated heading 'Zahlungseingang erfassen' duplicates the title. The information is valuable but would be easier to act on if split into when-to-use, parameter effects, and failure modes.

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 nested-body mutation tool with no output schema, the description covers everything an agent needs: plan requirement, both `kind` modes, overpayment resolution, refund limits, void-invoice handling, concurrency conflicts, and the downstream accounting effect.

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, but the description adds real meaning: it explains the interplay between `amount` and `overpayment` (what happens when the open remainder is exceeded, and that omitting `overpayment` yields 422), the cap on negative amounts, and that `amount`/`note` are omitted for `kind: skonto`. Some enum-level detail is left to the schema.

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 states a specific verb and resource: it records a (partial) payment against `invoice_id`, covering both invoices and positive corrections. It also clarifies the boundary against corrections, but it never contrasts itself with the sibling tools `amend_payment` or `cancel_payment`, so an agent must infer the split from names alone.

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?

Rich conditional guidance: negative amounts are refunds capped at the received sum, `kind: skonto` applies only to invoices with a skonto term and status `sent`/`partial`, and voided invoices only accept refunds. What is missing is explicit routing to alternatives (e.g. when to use `amend_payment` instead of a compensating entry).

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