Skip to main content
Glama

Check a SWIFT/BIC code and its bank from GLEIF

swift
Read-only

Checks a SWIFT/BIC code (8 or 11 characters): the format, bank code, country and its name, location, test and passive flags, branch, and the institution's LEI, legal name and address from GLEIF when a record carries that BIC. Without a GLEIF match the answer still gives the format check and institution null, with the reason. Pure code plus one GLEIF call, cached a day. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bic": "<bic>"
    },
    "name": "swift"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicYesA SWIFT/BIC code, 8 or 11 characters, e.g. DEUTDEFF or DEUTDEFF500

Output Schema

NameRequiredDescriptionDefault
bicNo
bankNo
validNo
branchNo
sourceNo
countryNo
testBicNo
locationNo
checkedAtNo
countryNameNo
institutionNo
primaryOfficeNo
institutionNoteNo
passiveParticipantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well past the readOnly/openWorld annotations: it discloses a one-day cache, the cost model ($0.002 per successful call via x402 USDC across multiple networks), that failed calls are not charged, and the latency/call profile ('pure code plus one GLEIF call'). It also predicts the failure shape when no GLEIF match exists, which is exactly the behavior an agent needs before spending money.

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 purpose and outcome enumeration, and the fallback/pricing details follow logically. The single sentence is dense and slightly run-on, but almost every clause (GLEIF enrichment, null case, caching, cost) carries information an agent would otherwise lack.

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?

For a one-parameter lookup with an output schema and readOnly annotations, this covers the remaining unknowns: enrichment source, fallback behavior with the reason field, caching, and payment/cost. Nothing an agent needs to decide whether and how to call it is missing.

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 coverage is 100% and already documents the single 'bic' parameter with the 8-or-11-character rule and examples, so the description cannot add much. It confirms the accepted lengths but introduces no new syntax or format guidance beyond the schema. Baseline 3 applies.

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 and resource ('Checks a SWIFT/BIC code') and enumerates exactly what is validated and returned: format, bank code, country, name, location, test/passive flags, branch, plus LEI, legal name and address enriched from GLEIF. This is clearly distinct from a generic 'lei' lookup because it is BIC-first with LEI as enrichment.

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

Usage Guidelines3/5

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

Usage is implied by the purpose: use this when you have a BIC and want validation plus institution data. The description also explains the degraded outcome when no GLEIF record exists, which helps an agent predict results. However, it never names an alternative or a when-not-to-use condition (e.g., looking up by LEI instead of BIC).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources