Skip to main content
Glama

Mansa African Financial Reference Data

by io.github.HeyZod

Look up an African bank by name or code

lookup_bank

Identify an African bank from any identifier you hold: its name, domestic sort/bank code, SWIFT/BIC code, or USSD shortcode. Works as a reverse lookup, so pass a bare SWIFT code like 'NLCBTZTX' to find out which institution it belongs to. Returns the bank's name, country, type, bank code, SWIFT/BIC, USSD shortcode and whether it supports mobile money.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10, max 50).
queryYesBank name, bank/sort code, SWIFT/BIC code, or USSD shortcode.
countryNoOptional ISO-2 country code to scope the search (e.g. NG, GH, KE, ZA, TZ).

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses what the tool returns (name, country, type, bank code, SWIFT/BIC, USSD, mobile money support) and highlights the reverse lookup behavior. No side effects or limitations are mentioned, but for a read-only lookup this is adequate.

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?

Two sentences with no fluff. The first sentence states purpose and scope; the second gives a concrete example and enumerates return fields. Everything earns its place, and the text is front-loaded with the primary verb and resource.

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?

Given the tool's moderate complexity, high schema coverage, and absence of an output schema, the description adequately covers what the tool does and what it returns. It doesn't explain how multiple matches are handled, but the 'limit' parameter and general lookup nature make it reasonably complete.

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 the baseline is 3. The description adds a concrete SWIFT example and clarifies the query types, but this is largely redundant with the schema's parameter description. No additional syntax or format details beyond the example.

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 clearly states the tool's purpose with a specific verb ('Identify') and resource ('African bank'), and lists the exact identifier types (name, sort/bank code, SWIFT/BIC, USSD). It distinguishes from siblings by emphasizing reverse lookup capability, making it unique among listed tools.

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

Usage Guidelines4/5

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

The description provides clear context on when to use the tool ('from any identifier you hold') and gives a concrete example of a SWIFT code reverse lookup. It doesn't explicitly name alternatives or state when not to use it, but the context is sufficient.

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

All Mansa African Financial Reference Data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct data type: currency, holidays, banks (list vs lookup), phone network, and NUBAN account resolution. Even the two bank tools are clearly separated by purpose—listing all institutions vs resolving one from an identifier. No tool overlaps meaningfully with another.

Naming Consistency5/5

All tool names follow a uniform verb_noun snake_case pattern (get_, list_, lookup_, resolve_), making the action and resource immediately clear. The convention is applied consistently across all six tools.

Tool Count5/5

With six tools, the server sits comfortably in the ideal 3-15 range. Each tool covers a distinct reference data need without bloat or redundancy, making the count well-scoped for the stated purpose.

Completeness4/5

The set covers core African financial reference data—currencies, holidays, banks, mobile networks, and NUBAN validation. However, there is no tool to list supported countries or all currencies, which would be a natural complement to the country-based lookups. This is a minor gap that agents can work around.

Resources