Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Record order payment

record_order_payment
Destructive

Records a full or partial payment against an order’s outstanding balance; amount is in minor currency units and capped at the balance due.

Instructions

Record a (possibly partial) payment against an order's outstanding balance. amount is in minor units of the order's currency and capped at the balance due.

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": {
      "orderId": "<orderId>",
      "amount": "<amount>",
      "reference": "<reference>"
    },
    "name": "record_order_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount in minor units of the order's currency (cents)
orderIdYes
providerNo
referenceYesPayment reference / receipt id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / amount / description
      Previous value: -"Amount in minor units (cents)"New value: +"Amount in minor units of the order's currency (cents)"
    • addedInput schema / required
      Added value: +[
      +  "orderId",
      +  "amount",
      +  "reference"
      +]
  2. First observedv0.73.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds a useful constraint (amount capped at the balance due) but says nothing about reversibility, idempotency of the reference field, or what happens on overpayment.

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?

Two tight sentences with the core action and the key constraint front-loaded; no filler or redundancy.

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 destructive mutation with no output schema and four parameters, the description is adequate but thin: it omits the role of provider and reference, error behavior on exceeding the balance, and any confirmation of what is returned.

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 50%, and the description only elaborates on amount (minor units, capped at balance due), which the schema already partly documents. The orderId, reference, and provider parameters receive no added meaning in the description.

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 ('Record a ... payment against an order's outstanding balance') and clarifies that partial payments are supported. It does not explicitly differentiate itself from siblings like mark_order_paid or record_order_invoice, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives such as mark_order_paid or refund_order. The only implied guidance is that partial payments are permitted, which an agent must infer.

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