Skip to main content
Glama
Tunzaa

Tunzaa MCP Server

Official
by Tunzaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

initiate_payment

Starts an M-Pesa or mobile money payment request via Malipo API, returning the response format needed to implement local payment flows and callbacks.

Instructions

Initiate a payment request (M-Pesa, etc.) via Malipo API. Call this to inspect the response structure needed to implement mobile money flows in your local code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesTransaction amount as a string to avoid precision issues (e.g., '5000').
addressNoOptional override for API base URL.
referenceYesUnique order reference from your system. Used to match callbacks.
customer_msisdnYesCustomer phone number in international format without '+' (e.g., 255700000000). Essential for Mobile Money push.
sandbox_scenarioNoIn sandbox mode, forces the outcome of the payment push. Maps to the X-Sandbox-Scenario header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • changedInput schema / properties / customer_msisdn / description
      Previous value: -"Customer phone number in local format (e.g., 0744550667). Essential for Mobile Money push."New value: +"Customer phone number in international format without '+' (e.g., 255700000000). Essential for Mobile Money push."
    • addedInput schema / properties / sandbox_scenario
      Added value: +{
+  "description": "In sandbox mode, forces the outcome of the payment push. Maps to the X-Sandbox-Scenario header.",
+  "enum": [
+    "success",
+    "failure"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it does not disclose that this is a state-changing, money-moving call, whether it requires auth, how the reference is used for callback matching/idempotency, or what the sandbox_scenario does to real vs. test funds. The 'inspect the response structure' framing actually understates the side effects rather than clarifying them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no padding, but the second sentence does not earn its place: it introduces ambiguity about the tool's nature instead of clarifying invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a financial mutation tool with no annotations and no output schema, the description omits auth requirements, environment/sandbox behavior, idempotency of the reference, and error semantics. An agent has too little to invoke this safely.

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 description coverage is 100%, so all five parameters including amount, reference, customer_msisdn, address, and sandbox_scenario are already documented in the schema. The description adds no parameter meaning beyond that, 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?

The first sentence names a specific verb and resource ('Initiate a payment request... via Malipo API') and even the payment rail (M-Pesa). It gives no differentiation from siblings like get_payment_status or handle_callback, and the second sentence ('inspect the response structure') blurs whether this is a live payment tool or a scaffolding/inspection helper.

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

Usage Guidelines2/5

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

It offers one usage claim ('Call this to inspect the response structure...') but never says when to use it versus get_payment_status or handle_callback, nor states prerequisites such as obtaining a token via get_token or running against a sandbox address.

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