Skip to main content
Glama

Mobile money

get_mobile_money_stats
Read-onlyIdempotent

Statistiques des paiements MOBILE MONEY (Wave, Orange Money, YAS, Kpay et portefeuilles ajoutés par la société : MTN MoMo, Moov Money…) sur les N derniers jours, aujourd'hui compris : montant et nombre de transactions par opérateur, part dans le chiffre d'affaires. Ventes en caisse et factures, comme le module Rapports. Idéal pour « combien j'ai encaissé via Wave/Orange Money ». (Lecture seule.)

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": "get_mobile_money_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLes N derniers jours, aujourd'hui compris

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description's "(Lecture seule.)" is redundant. Beyond that, it discloses real behavioral substance: the data window includes today, the figures cover both cash sales and invoices, and the breakdown is per operator including company-added wallets. It says nothing about auth needs or limits, but none are implied for a read-only stats call.

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?

The core purpose and timeframe come first, followed by the returned metrics, the operator list, and a use case. The parenthetical operator enumeration earns its place because it defines scope; only "(Lecture seule.)" is pure duplication of the annotations.

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?

With only one optional parameter and no output schema, the description does the necessary work of describing what the response contains (amount, count, revenue share per operator) and which underlying records feed it. The only gap is the absence of any routing guidance against related payment/revenue reporting tools.

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 days parameter is documented identically in the schema ("Les N derniers jours, aujourd'hui compris"). The description therefore adds no meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: statistics of mobile money payments per operator (amount, transaction count, revenue share) over the last N days. It even enumerates the operators covered, so an agent knows exactly what data comes back. It does not name any sibling, so overlap with tools like get_revenue_by_payment_method is left for the agent to resolve.

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

Usage Guidelines3/5

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

Offers one concrete positive use case ("combien j'ai encaissé via Wave/Orange Money") and frames it as an equivalent of the Rapports module, which implies context. However, it gives no when-not guidance and does not point to an alternative tool when a broader payment-method breakdown is needed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources