Skip to main content
Glama
momo-xof-mcp

momo-xof-mcp

momo_list_operators

Read-onlyIdempotent

Lists XOF-zone countries and their mobile money services with ISO codes, dialing formats, and phone number shapes so you can confirm payment scope and number validity before initiating a transaction.

Instructions

List the countries of the West African CFA franc (XOF) zone and the mobile money services available in each. For every one of the eight UEMOA countries it returns the ISO code, international dialing code, national number length and E.164 format, then the payment services on offer, and finally optional prefix hints. Purely static: no network call, no credentials needed. Use it before initiating a payment to check that a country and a service are in scope and that a phone number has the expected shape. Payment services are unrelated to number prefixes: independent wallets such as Wave run on any national mobile number. Prefix hints, when present, map a prefix to a telecom network only, are defeated by number portability, and must never be used to route a payment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "momo_list_operators"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoOptional ISO 3166-1 alpha-2 country code, to restrict the listing to a single country, for example 'BF' for Burkina Faso or 'CI' for Cote d'Ivoire. Case-insensitive. Omit it to list all eight UEMOA countries.

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?

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds beyond them: 'Purely static: no network call, no credentials needed,' which is actionable preconditions info. It also discloses a genuinely non-obvious behavioral caveat — prefix hints map to telecom networks only, are defeated by number portability, and must never be used to route a payment — which prevents a serious misuse.

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 scope of return data, then operational facts, then safety caveats — a sensible ordering with no filler. The final sentence is dense and carries three distinct warnings in one breath, which is efficient but slightly harder to parse.

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 static, single-optional-param lookup with an output schema, the description covers everything needed: what is returned, that no credentials are required, and how to safely interpret prefix hints. Return-value structure is described at a high level without duplicating the output schema.

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 schema already documents the optional `country` ISO code with examples and case-insensitivity, so the baseline is 3. The description does not mention the `country` filter at all; the phrase 'for every one of the eight UEMOA countries' only weakly implies the omit-to-list-all default already stated in the schema.

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: 'List the countries of the West African CFA franc (XOF) zone and the mobile money services available in each.' It then enumerates the exact returned fields (ISO code, dialing code, number length, E.164, payment services, prefix hints), which no sibling (momo_initiate_payment, momo_check_payment_status) does, so an agent can distinguish it immediately.

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 states the usage context: 'Use it before initiating a payment to check that a country and a service are in scope and that a phone number has the expected shape.' It also gives a strong when-not directive against routing payments by prefix. It stops short of naming a sibling tool outright, so the routing is implied rather than stated.

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