Skip to main content
Glama

Send payment

send_payment
Idempotent

Pay an approved purchase intent through a payout rail, sending funds to the vendor account on file. Retrying is safe because each intent is paid only once.

Instructions

Pay an approved intent through a payout rail (PayPal, Venmo, Stripe Connect, RazorpayX or Modern Treasury). The approved amount goes to the vendor's account on file in the policy; you can't choose the recipient. Each intent is paid at most once: calling again returns the existing payment, so it is safe to 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": {
      "intent_id": "<intent_id>"
    },
    "name": "send_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
intent_idYesThe intent_id returned by submit_purchase_intent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only supply idempotentHint=true, but the description adds real behavior: the recipient is fixed by policy and cannot be chosen, the amount is policy-determined, and a repeat call returns the existing payment rather than creating a second one, which explains retry safety in operational terms. That is substantive disclosure beyond the annotation, and it does not contradict it.

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?

Three tight sentences, front-loaded with the action and rails, then the recipient constraint, then the idempotency guarantee. Nothing is redundant and each sentence supplies new operational information.

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 single-parameter money-movement tool with no output schema, the definition covers who gets paid, how much, via which rails, and retry semantics. It leaves failure modes (rail errors, rejected intents) and the shape of the returned payment object unstated, which is a modest but real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and there is only one parameter, so the schema already carries the definition of intent_id. The description still adds meaning by constraining that the intent must be in an approved state and by tying it to the policy-defined recipient and amount, which is useful semantics beyond a bare string field.

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?

States a specific verb and resource ('Pay an approved intent') plus the concrete rail set (PayPal, Venmo, Stripe Connect, RazorpayX, Modern Treasury), which cleanly separates it from siblings like submit_purchase_intent and get_intent_status. An agent knows exactly what this does without opening the schema.

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?

The phrase 'Pay an approved intent' embeds the precondition that the intent must already have been submitted and approved, which implicitly routes the agent through submit_purchase_intent/compliance first. It does not explicitly name when NOT to call it or point at get_intent_status for status checks, so it stops short of full alternative routing.

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