Skip to main content
Glama

Record expense payment

crunch_add_expense_payment

Record full or partial expense payments, including date, amount, payment method, and paying bank account, credit card, or director, while keeping existing payments.

Instructions

Record that an expense was paid (fully or partly): date, amount, payment method and the bank account, credit card or director it was paid from. Existing payments are kept.

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": {
      "expense_id": "<expense_id>",
      "date": "<date>",
      "amount": "<amount>"
    },
    "name": "crunch_add_expense_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesPayment date (YYYY-MM-DD)
amountYesAmount paid, for example 120.00
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
person_idNoFor DIRECTORS_EXPENSES: the director who paid (see crunch_list_persons)
expense_idYesExpense ID (see crunch_list_expenses)
credit_card_idNoCredit card the payment was made with (see crunch_list_credit_cards)
payment_methodNoPayment method name, for example EFT, CASH or DIRECTORS_EXPENSES (default EFT; see crunch_list_payment_methods)
bank_account_idNoBank account the payment went through (see crunch_list_bank_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, non-idempotent write, and the description adds meaningfully that "existing payments are kept", clarifying additive partial-payment behavior. It does not warn that non-idempotent retries could create duplicate payments, nor does it say how the expense balance or status changes as a result.

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?

Two tight sentences with no filler; the payment action and the partial-payment allowance are front-loaded. The trailing "Existing payments are kept" clause is slightly ambiguous (kept alongside the new one, or untouched?) but is short enough to earn its place.

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?

With full schema description coverage, a dry_run preview parameter and annotations carrying the safety profile, the description supplies enough for correct invocation. The remaining gap is behavioral outcome (effect on expense balance/status, duplicate-payment risk), which is minor for a well-documented 8-parameter write.

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?

Schema coverage is 100% and every parameter is already documented inline, including the director/credit-card/bank-account routing and the dry_run preview. The description's field list (date, amount, payment method, funding source) restates the schema rather than adding new semantics, so the baseline 3 applies.

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?

States a specific verb and resource ("Record that an expense was paid") and scopes it to a single existing expense, covering both full and partial payments. The resource distinction makes it separable from the invoice-payment sibling, though no sibling is named explicitly.

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?

Usage is only implied: the required expense_id and payment fields signal that this attaches a payment to an existing expense. There is no explicit guidance on when to use this versus crunch_update_expense or crunch_add_invoice_payment, and no mention of prerequisites such as the expense needing to be unpaid.

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

Deploy Server

Other Tools