momo-mcp

Request a MoMo payment

momo_request_to_pay

Destructive

Request a Mobile Money payment from a subscriber's phone and receive a reference ID to track its PENDING status until the payer approves.

Instructions

Ask a subscriber to approve a payment on their phone. Returns a referenceId; the payment is PENDING until they approve, so poll momo_payment_status. In a production environment this collects REAL money and requires explicit confirmation from the human you are working for - never supply the confirmation phrase on your own initiative.

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": {
      "amount": "<amount>",
      "phoneNumber": "<phoneNumber>"
    },
    "name": "momo_request_to_pay"
  }
}

Input Schema

Name	Required	Description
`amount`	Yes	Amount in major units, e.g. 25.50
`confirm`	No	Required in production only. Must be exactly "CONFIRM LIVE PAYMENT".
`payeeNote`	No	Kept on your side, max 160 chars
`externalId`	No	Your own order reference
`phoneNumber`	Yes	Payer's number, digits only, no +
`payerMessage`	No	Shown to the payer, max 160 chars

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description adds real value on top: it discloses the return value (referenceId), the PENDING-until-approved lifecycle, and the critical safety constraint that production moves real money and the confirmation phrase must never be supplied autonomously. That last point is behavior an agent cannot infer from any structured field.

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 sentences, zero waste. The action and its result lead, then the lifecycle and safety constraint follow in priority order.

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?

There is no output schema, and the description compensates by naming the referenceId return and the PENDING state, plus the polling path. Combined with annotations covering the safety profile, an agent has everything needed to call this correctly and responsibly.

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%, so parameters are already well documented and the baseline is 3. The description adds meaning beyond the schema for the `confirm` parameter by framing it as a human-authorization gate the agent must not self-supply, which is semantic guidance the schema's 'must be exactly ...' text does not convey.

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 ('Ask a subscriber to approve a payment on their phone') and immediately distinguishes itself from the sibling momo_payment_status by naming it as the follow-up polling step. An agent knows exactly what this initiates 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?

Explicitly routes the agent to momo_payment_status for follow-up and states the production precondition (explicit human confirmation). It stops short of naming any alternative initiation path or when-not-to-call condition, but the sequencing and gating guidance is clear.

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

Deploy Server