Skip to main content
Glama

IBAN Validator - check IBANs, bank name and BIC (bulk)

iban_validator
Read-onlyIdempotent

Validate up to 1,000 IBANs per call for every IBAN country (length, country format, mod-97 check digits), split into bank code, branch and account, SEPA flag, and for German IBANs the bank name, city and BIC from the official Deutsche Bundesbank bank code file. Spaces/dashes/lower case accepted. Runs on our server, nothing stored, < 0.1 s. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/iban-validator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "iban": "DE89 3704 0044 0532 0130 00"
    },
    "name": "iban_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
ibanNoOne IBAN, e.g. DE89 3704 0044 0532 0130 00
ibansNoOr a list of up to 1,000 IBANs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/open-world safety, but the description adds real value beyond them: nothing is stored, results are returned in under 0.1 s, free tier is 25 calls/day per IP, and paid calls cost $0.001 via x402. It also discloses the German-only enrichment of bank name/city/BIC, which the agent could not infer from annotations.

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?

Single dense paragraph, front-loaded with the core capability and validation scope before pricing and infrastructure details. Nearly every clause carries information, though the pricing/x402 URL sentence is long and could be tightened.

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?

With no output schema, the description must convey return content, and it does (bank code, branch, account, SEPA flag, German bank name/city/BIC). Remaining gap is failure semantics: it does not say whether invalid IBANs produce per-item errors alongside valid results in a bulk call.

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 coverage is 100%, so the baseline is 3, but the description adds meaningful semantics the schema lacks: the 1,000-item bulk ceiling and the input normalization tolerance for spaces, dashes, and lower case. It does not clarify whether iban and ibans are mutually exclusive or what happens on mixed input, keeping it below a 5.

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+resource ("Validate ... IBANs") and immediately scopes it: length, country format, mod-97 check digits, plus parsing into bank code/branch/account, SEPA flag, and German bank name/BIC. An agent can distinguish this from siblings like sepa_xml or business_check from the description alone.

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?

Gives practical preconditions (accepts spaces/dashes/lower case, 1,000 IBAN cap) and implies the use case (checking IBANs before payments), but never says when to prefer or avoid it relative to alternatives such as sepa_xml or business_check. Usage is implied rather than explicitly routed.

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