Skip to main content
Glama

Verify Bank Account

monei_verify_bank_account
Read-onlyIdempotent

Verify a Nigerian bank account before sending naira to confirm the account holder's name and avoid transferring to the wrong account. Provide account number and bank code to get the account name.

Instructions

Verifies a Nigerian bank account number and returns the account holder's name.

Always call this before sending naira to a bank account. Surfacing the account name to the user before they confirm the transaction prevents sending to the wrong account.

Args:

  • accountNumber (string): 10-digit Nigerian bank account number

  • bankCode (string): Bank code from monei_get_banks (e.g. "058" for GTBank)

Returns: { "accountName": string, "accountNumber": string, "bankCode": string }

Examples:

  • Before sending to 0123456789 at GTBank -> call this with accountNumber="0123456789", bankCode="058"

  • User says "send to my GTBank account 0123456789" -> verify first, show account name, confirm before sending

Error handling:

  • Returns error if the account number does not exist at the given bank

  • Returns error if the bank code is invalid (call monei_get_banks to find valid codes)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bankCodeYesBank code (e.g. '058' for GTBank, '033' for UBA). Call get_banks to get the full list of bank codes.
accountNumberYesNigerian bank account number (exactly 10 digits)

Schema Changelog

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

  1. First observedv1.3.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds meaningful behavioral context on top: error outcomes for invalid account numbers or bank codes, and the recommended user-confirmation workflow. No contradiction with annotations found.

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?

Well-organized: a one-sentence summary, clear when-to-use rationale, structured args, return shape, examples, and error handling. Every section earns its place; the length is justified for a safety-relevant verification tool.

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 output schema, the description fully covers the return format using a JSON example. It also covers required parameters, real-world examples, and failure modes, making the tool safe and self-contained for an agent to invoke correctly.

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 documents both parameters fully (100% coverage). The description adds practical value by restating that accountNumber is a 10-digit Nigerian account number, giving a concrete bankCode example ('058' for GTBank), and tying bankCode to monei_get_banks.

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 ('Verifies'), a clear resource ('Nigerian bank account number'), and the key outcome (returns the account holder's name). This immediately distinguishes it from siblings like monei_get_banks (bank metadata) and monei_send_naira_to_bank (sending).

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?

Explicitly instructs to call this before sending naira to a bank account and explains why: surfacing the account name prevents sending to the wrong account. It also points to monei_get_banks as the source for valid bank codes, giving clear routing guidance.

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