Skip to main content
Glama

Record payment (invoicing)

solo_record_payment

Money arrived. Recording it and deciding what it settles are two acts. Never guess which invoice a payment is for — unapplied is a valid, visible state. Ask, or leave it unapplied. Effects: payment recorded as unapplied.

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": "solo_record_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount received. In cents (integer minor units) — 1250 means $12.50.
methodNoHow it arrived.
currencyNoCurrency the money arrived in, ISO 4217. Defaults to the company default; a payment only ever settles invoices in its own currency.
referenceNoTransfer reference, check number — exactly as shown.
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

A3.9/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent, closed-world mutation. The description contributes beyond that with an explicit postcondition ('recorded as unapplied') and a domain rule that protects data quality. It doesn't flag the duplicate-payment risk implied by idempotentHint=false, which would have made it a 5.

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?

Short and front-loaded — the outcome and the effects line come first, the guardrail rule sits in the middle. The staccato fragments ('Money arrived.') are stylistic but cost little; nearly every sentence carries a distinct instruction.

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?

For a write tool with no output schema, the description covers the essential mystery an agent can't get from fields: whether the payment auto-settles an invoice. It doesn't say what the call returns (payment id? applied amount?) or how to then apply it, so a small gap remains.

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% — cents-as-integer, ISO currency, ISO date, and the method enum are all documented in the schema. The description adds no parameter-level information beyond that, 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?

The description makes clear this records a received payment and, crucially, that recording and applying are separate acts — which is the key distinction from its sibling solo_apply_payment. It does not name that sibling explicitly, relying on the reader to infer it from 'deciding what it settles are two acts.'

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?

It gives real usage policy: never guess which invoice a payment belongs to, ask the user or leave it unapplied because unapplied is a valid visible state. What's missing is an explicit named alternative (solo_apply_payment) for the follow-up step, so the routing guidance is behavioral rather than tool-directed.

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.