Skip to main content
Glama
Sign In
momo-mcp

momo-mcp

by mbilisphe13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Show MoMo environment

momo_environment
Read-only

Reports which MTN MoMo environment the server targets, whether it moves real money, and configured limits; call before any payment to confirm sandbox or production.

Instructions

Report which MTN MoMo environment this server targets, whether it moves real money, and the configured limits. Call this first, and always before any 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_environment"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful context by saying it reports whether the server moves real money and what limits apply — a behavioral trait the agent needs before transacting. It does not describe the response shape in detail, which keeps it just short of a 5.

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?

One compact sentence with the effect first and the calling instruction second. Every clause carries load: what it reports, why it matters (real money), and when to call it.

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?

With no parameters and no output schema, the description must convey what comes back, and it does — environment, real-money status, and configured limits. That is everything an agent needs to decide to call it before a payment.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for 0 params applies. The description correctly stays silent on inputs rather than inventing them.

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+resource: reports the target MTN MoMo environment. It further pins down the exact scope (real-money status and configured limits), which clearly separates it from sibling tools like momo_account_balance or momo_request_to_pay.

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

Usage Guidelines5/5

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

Gives an explicit trigger and ordering rule: 'Call this first, and always before any payment.' The condition that selects it over every payment sibling is stated directly, leaving nothing to inference.

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