Skip to main content
Glama

Send Naira to Monei User

monei_send_naira_to_user
Destructive

Send NGN to another Monei user using their email or phone number. Provide the amount, recipient, and 4-6 digit transaction PIN after confirming sufficient wallet balance.

Instructions

Sends NGN to another Monei user identified by their email address or phone number.

This is faster than a bank transfer and works instantly between Monei users. Use this when the recipient is identified by email or phone rather than a bank account number.

Before calling:

  1. Confirm sufficient NGN balance using monei_get_wallet

  2. Ask for the user's transaction PIN if not provided — never store or log it

Args:

  • amount (number): Amount in NGN to send (e.g. 5000 for ₦5,000)

  • receiver (string): Recipient's registered Monei email or phone number (e.g. "john@gmail.com" or "08012345678")

  • transactionPin (string): User's 4-6 digit transaction PIN — ask for this at runtime

Returns: { "reference": string, "status": string, "amount": number, "currency": "NGN", "receiver": string, "createdAt": string }

Examples:

Error handling:

  • Returns error if the receiver is not a registered Monei user

  • Returns error if insufficient balance

Security: Never log or store the transactionPin. Pass it directly to this call only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount in NGN to send (e.g. 5000 for ₦5,000)
receiverYesThe recipient's registered Monei email address or phone number (e.g. john@gmail.com or 08012345678)
transactionPinYesUser transaction PIN (4-6 digits). Required for all money movement operations. Prompt the user for this if not provided — never store or log it.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.3.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations signal that this is a non-read-only, destructive operation, and the description adds meaningful behavior beyond those flags: transfers are 'instant between Monei users,' it returns errors for unregistered receivers or insufficient balance, and it warns never to store or log the transaction PIN. This aligns with the annotations and gives an agent a complete safety picture.

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 purpose is front-loaded, and the rest is organized into scannable sections: Before calling, Args, Returns, Examples, Error handling, and Security. Each section is purposeful for a money-movement tool and avoids unnecessary fluff.

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?

Even though there is no output schema, the description supplies the exact return shape, common error cases, required preconditions, and security handling. For a 3-parameter money-transfer tool, nothing an agent needs to select and invoke it correctly is missing.

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 input schema already covers all three parameters at 100%, so the baseline is 3. The description adds real value with natural-language examples that map user phrases like 'Send ₦5,000 to john@gmail.com' to the receiver parameter, and it emphasizes that the transactionPin must be asked for at runtime and passed directly without logging.

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?

The description opens with a specific verb and resource: 'Sends NGN to another Monei user identified by their email address or phone number.' It clearly distinguishes this tool from bank transfers, crypto sends, and bill payments, so an agent can tell what it does without comparing schemas.

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?

The description explicitly states when to use it: 'Use this when the recipient is identified by email or phone rather than a bank account number.' It also gives practical prerequisites, including confirming sufficient balance with monei_get_wallet and asking for the transaction PIN at runtime.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mr-Money01/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server