Skip to main content
Glama

Record payment (order to cash)

o2c_record_payment

Record cash received from a customer. Recording the receipt and deciding what it settles are two acts, and this is only the first. A payment that arrives without a remittance advice sits as unapplied cash — which is the correct state, and visible in o2c_unapplied_cash. Never guess which invoice a payment is for to make the aging look tidy. Effects: payment recorded as unapplied cash.

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": {
      "customer_id": "<customer_id>",
      "amount": "<amount>"
    },
    "name": "o2c_record_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount received. In cents (integer minor units) — 1250 means $12.50.
methodNoHow it arrived.
referenceNoCheck number, wire reference, remittance id — exactly as printed.
customer_idYesWho paid. An existing customer id.
received_atNoValue date. Defaults to today. ISO date, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

It adds meaningful behavior beyond the annotations: the payment is recorded as unapplied cash and is not automatically matched to an invoice. That is useful state disclosure for a non-destructive mutation. It could do more by noting the non-idempotent hint's implication, such as duplicate-payment handling, but the core effect is clear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded and the explanatory sentences are short and purposeful. The warning about not guessing invoice matches earns its place by preventing a common misuse.

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 fully described schema with annotations and no output schema, the description supplies the key workflow context: what this step does, what it does not do, and where the result is visible. Nothing critical is missing for correct invocation.

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 100%, so all five parameters already have clear meanings and formats in the schema. The description does not add parameter-level guidance beyond what the schema provides, which is appropriate but not value-adding.

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?

The description states a specific verb and resource: recording cash received from a customer. It explicitly distinguishes this act from deciding what the payment settles, making clear it is the receipt step only, not the application step handled by siblings such as o2c_apply_payment.

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?

It says exactly when to use this tool and when not to: record the receipt, but never guess which invoice a payment belongs to in order to tidy aging. It points to o2c_unapplied_cash as the visible state and implicitly routes settlement to a separate step.

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.