Skip to main content
Glama

Record a cash payment

cash_payment_record

Records a completed cash payment settling a member's full net debt to another member without moving funds; use the expected balance to catch debt changes.

Instructions

Records a cash payment that already happened over the whole current net debt from fromMemberId to toMemberId; ManaWG moves no money. Use it once the debt was handed over; to mark only selected shares use settlement_commit or expense_split_settle, to take a wrong entry back use cash_payment_void. The caller must be one of the two members (otherwise not_party_to_debt), both active in the flat (member_not_in_wg). expectedNetCents guards against a changed debt: 409 settlement_changed means run settlement_preview again. Notifies the other member and writes an audit entry.

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": {
      "fromMemberId": "<fromMemberId>",
      "toMemberId": "<toMemberId>",
      "expectedNetCents": "<expectedNetCents>"
    },
    "name": "cash_payment_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
currencyNoCurrency of the debt that was paid.EUR
toMemberIdYesMember who received the cash, from members_list.
fromMemberIdYesMember who paid the cash and owed the money, from members_list.
expectedNetCentsYesnetCents from settlement_preview for the same members and currency: the net debt in cents you expect to settle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / currency / description
      Added value: +"Currency of the debt that was paid."
    • addedInput schema / properties / expectedNetCents / description
      Added value: +"netCents from settlement_preview for the same members and currency: the net debt in cents you expect to settle."
    • addedInput schema / properties / fromMemberId / description
      Added value: +"Member who paid the cash and owed the money, from members_list."
    • addedInput schema / properties / toMemberId / description
      Added value: +"Member who received the cash, from members_list."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, idempotent=false, destructive=false), the description discloses that no money actually moves, that the caller must be one of the two members with named error codes (not_party_to_debt, member_not_in_wg), that expectedNetCents is an optimistic guard whose failure returns 409 settlement_changed, and that the call notifies the other member and writes an audit entry. This is exactly the behavioral context annotations cannot convey.

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 action and the no-money-moved caveat, then routes alternatives and error handling in a single dense paragraph with no filler. The 'from fromMemberId to toMemberId' phrasing is slightly awkward and the paragraph is long, but every clause carries operational information.

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?

With no output schema and a write operation, the description supplies the preconditions, the two relevant failure modes with their remedies, the side effects on other members, and the audit trail. An agent has enough to decide whether to call it and how to react to failure without further tools.

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 baseline is 3, but the description adds cross-field meaning the schema cannot: the payment settles the whole current net debt between the two named members, and expectedNetCents is a staleness guard tied to settlement_preview rather than a free-form amount. It does not elaborate wgCode omission or currency selection beyond what the schema already says.

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 ('Records a cash payment that already happened over the whole current net debt from fromMemberId to toMemberId') and immediately bounds the scope with 'ManaWG moves no money.' It names the sibling tools it is not (settlement_commit, expense_split_settle, cash_payment_void), so an agent can distinguish it 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 Guidelines5/5

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

Gives explicit when-to-use ('once the debt was handed over') and when-not alternatives for two different cases: partial settlement goes to settlement_commit or expense_split_settle, reversals go to cash_payment_void. It also states caller eligibility and the recovery path on 409 settlement_changed.

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