Look up African banks and mobile-money institutions by country (NIBSS sort codes, SWIFT/BIC, USSD) or a single bank code (e.g. 058 = GTBank).
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | Optional single bank code, e.g. 058. | |
| country | No | Optional ISO-2 country filter. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, non-destructive behavior, so the description does not need to repeat safety traits. It adds value by explaining the two lookup modes (country vs. single code) and the types of identifiers returned, giving the agent useful context beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence that efficiently communicates the tool's scope, search modes, and an example. No redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with two optional parameters and no output schema, the description is mostly complete. It does not state behavior when both parameters are omitted, which is a minor gap, but the overall usage is clear enough 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.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already covers both parameters with descriptions (100% coverage). The description reinforces their meaning by mentioning 'country' and 'single bank code', and adds a concrete example ('058 = GTBank') that clarifies the format of the code parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Look up African banks and mobile-money institutions' with specific search criteria (country or code). It includes concrete data types (NIBSS sort codes, SWIFT/BIC, USSD) and an example, making it distinct from sibling market-data tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool by specifying two filtering modes (by country or by single code). It does not explicitly mention alternatives or exclusions, but the sibling tools are clearly for exchange/financial data, so the context is sufficiently clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are largely distinct in purpose, with clear resource-specific patterns like get_african_exchange_stocks vs get_ngx_all_stocks. Some overlap exists between generic African tools and NGX-specific convenience wrappers (e.g., get_market_open_status vs get_ngx_market_status), and get_african_policy_rates overlaps with get_country_macro_indicators on inflation/policy rate data, but descriptions clarify these boundaries.
All tools follow a consistent get_<domain>_<object> snake_case pattern, with plural/singular used appropriately (e.g., get_african_exchanges vs get_african_exchange). No mixed conventions or vague generic verbs—every name clearly signals its resource.
At 21 tools, the server is on the heavier side but within the 16-25 borderline zone. Each tool addresses a distinct data need for the broad African-markets domain, though some redundancy from NGX-specific wrappers (e.g., get_ngx_market_status vs get_market_open_status) could be trimmed.
The server covers a wide range of market data: exchanges, indices, stocks, FX, macro indicators, yield curves, and bank data. Minor gaps include lack of single-stock price/history for non-NGX exchanges and limited historical data beyond Nigeria's macro series, but core market-analysis workflows are well supported.
