Skip to main content
Glama
momo-xof-mcp

momo-xof-mcp

momo_check_payment_status

Read-onlyIdempotent

Check the status of a previously requested mobile money payment by merchant reference or transaction ID. Returns a final or pending outcome without moving funds.

Instructions

Check what became of a payment you requested earlier. Read-only: it never moves money and never changes anything. Accepts either the merchant reference you supplied when initiating, or the transaction_id returned then. Returns a stable status plus the aggregator's own status and code, and says whether the outcome is final. A payment that was requested but never completed by the customer ends up FAILED, which is final — it does not stay pending forever. The customer's phone number is returned masked, never in full.

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": {
      "reference": "<reference>"
    },
    "name": "momo_check_payment_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceYesEither the merchant reference you supplied to momo_initiate_payment, or the transaction_id it returned. Both address the same payment.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses real behavior: the response carries a stable status plus the aggregator's own status and code, an explicit finality flag, the terminal semantics of FAILED for abandoned payments, and that the phone number is masked. The terminal-state rule is exactly the kind of context an agent needs to avoid polling forever.

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?

Front-loaded with purpose, then behavior, then input forms. Well structured with no wasted clauses, though 'never moves money and never changes anything' largely duplicates the readOnlyHint annotation and could be trimmed to one clause.

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 single-parameter read tool this is thorough: input forms, status semantics, finality, terminal failure states, and PII handling are all covered, even though the output schema would have excused some of that detail.

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% and the single parameter is already documented as accepting either a merchant reference or a transaction_id. The description restates this and adds only that 'both address the same payment', so baseline 3 is appropriate.

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?

Opens with a specific verb and resource: 'Check what became of a payment you requested earlier.' The 'you requested earlier' scope cleanly separates it from momo_initiate_payment, and an agent can pick the right tool 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?

Usage context is clear: this is the follow-up to a previously initiated payment, addressed by either reference form. It does not explicitly name siblings or state when-not to use it, but the temporal framing ('earlier', 'when initiating') makes the division of labor obvious.

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