Skip to main content
Glama

banking-intelligence

by ai.ohmyfin
OverviewDiscussionsAdmin

Banks Using a Correspondent

banks_using_correspondent
Read-only

Reverse SSI lookup — find banks that use a given correspondent for a currency.

Given a correspondent BIC, currency, and origin country, returns the banks in that country that have a declared nostro at the correspondent for that currency. Inverse of ssi_lookup.

Returns only swift + name per bank — to retrieve the account number, intermediary chain, or other SSI details for a specific bank from the result list, call ssi_lookup(bank_swift, currency) on it.

Country and currency are required (not optional) — both bound the result set and the query is rejected without them.

Requires an API key with an active PRO, VIP, or FI subscription.

Examples: banks_using_correspondent("IRVTUS3N", "USD", "AE") banks_using_correspondent("CITIUS33", "USD", "SA", name_prefix="AL")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResult page, 1-4 (default 1). Any other value is refused.
api_keyNoYour Ohmyfin API key (prod-...). Optional here: it can be sent instead as a KEY header or an Authorization: Bearer header. What the tool requires of the key is in its description.
countryYesISO 3166-1 alpha-2 country code of the client banks (e.g. "AE").
currencyYesISO 4217 currency code (e.g. "USD").
name_prefixNoOptional prefix on the client bank's name (e.g. "AL").
correspondent_swiftYesBIC of the correspondent bank, 8 or 11 characters (e.g. "IRVTUS3N").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / api_key / description
      Added value: +"Your Ohmyfin API key (prod-...). Optional here: it can be sent instead as a KEY header or an Authorization: Bearer header. What the tool requires of the key is in its description."
    • addedInput schema / properties / correspondent_swift / description
      Added value: +"BIC of the correspondent bank, 8 or 11 characters (e.g. \"IRVTUS3N\")."
    • addedInput schema / properties / country / description
      Added value: +"ISO 3166-1 alpha-2 country code of the client banks (e.g. \"AE\")."
    • addedInput schema / properties / currency / description
      Added value: +"ISO 4217 currency code (e.g. \"USD\")."
    • addedInput schema / properties / name_prefix / description
      Added value: +"Optional prefix on the client bank's name (e.g. \"AL\")."
    • addedInput schema / properties / page / description
      Added value: +"Result page, 1-4 (default 1). Any other value is refused."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses the narrowed return shape ('only swift + name per bank'), the subscription requirement (PRO, VIP, or FI API key), the mandatory-parameter rejection behavior, and the paging bound of 1-4. This is exactly the behavioral context annotations cannot carry.

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

Conciseness4/5

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

Front-loaded with the core purpose, then layered detail and examples. Slightly long, and the 'Country and currency are required (not optional)' line partly restates the schema's required array, but the reason given (bounding the result set) earns its place.

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?

Despite an output schema existing, the description usefully summarizes the return shape and routes the agent to ssi_lookup for detail. Auth tier, required params, and pagination limits are all covered, leaving nothing an agent needs 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?

Schema description coverage is 100%, so the baseline is 3. The description adds real value on top: it explains why country and currency are required (they bound the result set) and supplies worked examples showing correspondent_swift, currency, country, and name_prefix combined.

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?

Opens with a specific verb+resource and scope: 'Reverse SSI lookup — find banks that use a given correspondent for a currency.' It explicitly names its sibling relationship ('Inverse of ssi_lookup'), letting an agent distinguish it from ssi_lookup without opening either schema.

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?

States the exact when-to-use case, the mandatory inputs, and the explicit follow-up path: call ssi_lookup(bank_swift, currency) on a result to get account numbers or intermediary chains. Exclusions are covered by the required country/currency constraint and the 'query is rejected without them' note.

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

All banking-intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources