Skip to main content
Glama

record_invoice_payment

Idempotent

Record money already received for a sent invoice. Use its currency minor units and the business-local date. Recording can expire an open online checkout session. Reuse the same paymentId on retry.

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": {
      "paymentId": "<paymentId>",
      "id": "<id>",
      "amount": "<amount>",
      "method": "<method>",
      "receivedOn": "<receivedOn>"
    },
    "name": "record_invoice_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
noteNo
amountYes
methodYes
paymentIdYes
receivedOnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnly=false, idempotent=true, destructive=false and openWorld=true, so the bar is lower, but the description still adds real value: it warns that recording can expire an open online checkout session, a side effect no annotation conveys. The retry instruction tied to paymentId makes the idempotency hint concrete and actionable. It omits permission requirements and whether the entry can later be reversed.

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?

Four short sentences, front-loaded with the core action and then the constraints that matter most (units, date basis, side effect, retry). Every sentence carries information, though 'Use its currency minor units' has an ambiguous pronoun antecedent ('its') that could briefly confuse an agent about which object's currency applies.

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

Completeness3/5

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

For a 6-parameter mutation with no output schema and no documented parameters, the description covers the highest-risk behavior (checkout session expiry) and the retry contract, which are the things an agent most needs. It leaves notable gaps for a financial write: no statement of what is returned, how partial or over-payments are treated, or what 'id' refers to.

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 description coverage is 0%, so the description must carry the parameter burden, and it only partially does — it clarifies the unit for 'amount' (currency minor units), the timezone basis for 'receivedOn' (business-local date), and the retry semantics of 'paymentId'. The required 'id' field (presumably the invoice), the 'method' enum values, and the optional 'note' get no explanation beyond their schema types.

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 gives a specific verb and resource — recording received money against a sent invoice — and the qualifier 'already received' plus 'sent invoice' narrows it away from payment-link creation or draft work. It stops short of naming a sibling tool explicitly, so an agent must infer the boundary with record_appointment_payment or list_invoice_payments from the noun alone.

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?

'Record money already received for a sent invoice' implies the prerequisite state (invoice sent, funds already collected offline), which is useful context for use. However, there is no explicit when-not guidance — nothing says to use a payment link for online collection or remove_invoice_payment to reverse an entry — so routing is left to inference.

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