Skip to main content
Glama

validate_iban

Validate an IBAN checksum and format for 80+ countries. Decode its components: country code, bank code, and account number.

Instructions

Validate an IBAN (International Bank Account Number) and decode its components.

Validates the IBAN checksum algorithm and structure for 80+ participating
countries. Returns decoded bank and account information derived from the
IBAN format (note: does not confirm the account is live or funded).

Args:
    iban: IBAN string to validate. Spaces are allowed and ignored
          (e.g. 'GB29 NWBK 6016 1331 9268 19' or 'GB29NWBK60161331926819').

Returns:
    valid (bool): True if the IBAN passes checksum and format validation.
    iban: Normalised IBAN with no spaces.
    country_code: ISO country code.
    check_digits: The two check digits (positions 3-4).
    bban: Basic Bank Account Number (country-specific format).
    bank_code: Bank identifier extracted from the BBAN (where applicable).
    account_number: Account number portion of the BBAN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ibanYes
Behavior5/5

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

With no annotations, the description fully covers behavioral traits: validates checksum/structure, allows spaces, returns decoded components, and explicitly states it does not check account activity. No contradictions.

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?

The description is well-structured with a summary, note, args, and returns sections. It is concise with no redundant sentences; every sentence adds value.

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?

Given the tool has one parameter and no output schema, the description is thorough. It lists all return fields (valid, iban, country_code, etc.), explains the validation scope, and notes limitations. It is complete for its purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides no description for the 'iban' parameter (0% coverage). The description adds detailed semantics: explanation of the parameter, that spaces are allowed and ignored, and provides example values, significantly aiding the agent.

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 validates and decodes IBANs, with a specific verb and resource. It distinguishes itself from siblings by focusing on IBAN specifically, which is different from email validation or DNS lookups.

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?

It explains what the tool validates (checksum and structure) and explicitly notes it does not confirm account existence ('does not confirm the account is live or funded'). This provides when-to-use and limitations, though it lacks explicit when-not-to-use mentions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ForeverTools/kiprio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server