Skip to main content
Glama

ToolForte

IBAN Validator

validate_iban
Read-onlyIdempotent

Check whether an IBAN is well formed: the mod-97 checksum, the country code, the length that country's IBAN must have, and whether every position holds the kind of character that country allows there (mod-97 turns letters into numbers, so on its own it cannot see a capital O typed in place of a zero). Returns validity, country, and where known the bank identifier printed inside the IBAN. This is a format check, not a bank check: a passing IBAN can still name a bank code that never existed or has since merged away, and says nothing about whether the account exists or can receive a payment. For twelve countries it also verifies the national check digit that the bank computes over the bank code and account number (BE, FR, MC, ES, IT, SM, PT, SI, PL, TN, EE, HU); nationalCheck 'failed' there means the number is very probably invented, since that digit cannot be back-computed the way the mod-97 pair can. Absent nationalCheck means not checked, never approved. For Dutch IBANs it also names the institution behind the four-letter bank code, including codes that no longer issue accounts; an unrecognised code does not make the IBAN invalid. A territory that borrows another country's IBAN (Reunion, Guernsey, Aland and the like) is reported with the prefix it actually uses, since no IBAN starts with RE or GG. Never guess whether an IBAN is well formed: use this tool. Do not present a pass as confirmation that money can be sent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ibanYesThe IBAN to validate

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ibanNo
validNoWhether the input passed every check
resultNoThe result, when it is not an object
countryNo
bankCodeNo
checkDigitsNo
countryNameNo
institutionNo
accountNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "accountNumber": {
      +      "type": "string"
      +    },
      +    "bankCode": {
      +      "type": "string"
      +    },
      +    "checkDigits": {
      +      "type": "string"
      +    },
      +    "country": {
      +      "type": "string"
      +    },
      +    "countryName": {
      +      "type": "string"
      +    },
      +    "iban": {
      +      "type": "string"
      +    },
      +    "institution": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "kind": {
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "result": {
      +      "description": "The result, when it is not an object"
      +    },
      +    "valid": {
      +      "description": "Whether the input passed every check",
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "https://json-schema.org/draft/2020-12/schema",
      -  "additionalProperties": {},
      -  "properties": {
      -    "accountNumber": {
      -      "type": "string"
      -    },
      -    "bankCode": {
      -      "type": "string"
      -    },
      -    "checkDigits": {
      -      "type": "string"
      -    },
      -    "country": {
      -      "type": "string"
      -    },
      -    "countryName": {
      -      "type": "string"
      -    },
      -    "iban": {
      -      "type": "string"
      -    },
      -    "institution": {
      -      "additionalProperties": {},
      -      "properties": {
      -        "kind": {
      -          "type": "string"
      -        },
      -        "name": {
      -          "type": "string"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "result": {
      -      "description": "The result, when it is not an object"
      -    },
      -    "valid": {
      -      "description": "Whether the input passed every check",
      -      "type": "boolean"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "accountNumber": {
      +      "type": "string"
      +    },
      +    "bankCode": {
      +      "type": "string"
      +    },
      +    "checkDigits": {
      +      "type": "string"
      +    },
      +    "country": {
      +      "type": "string"
      +    },
      +    "countryName": {
      +      "type": "string"
      +    },
      +    "iban": {
      +      "type": "string"
      +    },
      +    "institution": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "kind": {
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "result": {
      +      "description": "The result, when it is not an object"
      +    },
      +    "valid": {
      +      "description": "Whether the input passed every check",
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), yet the description adds substantial behavioral detail beyond them: which 12 countries get national check-digit verification, that 'failed' implies a fabricated number while absent means unchecked-not-approved, and that territories are reported under the prefix actually used. This is exactly the added context annotations cannot supply.

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?

The core capability and return values are front-loaded, and the caveats that follow are each distinct (mod-97 letter/zero ambiguity, national check digits, Dutch institution codes, territory prefixes). It is long for a validator, with some redundancy between the 'not a bank check' caveat and the closing 'do not present a pass as confirmation', but almost every sentence carries non-repeating information.

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 fully explains the semantic meaning of each returned field (including the ambiguous 'absent nationalCheck') and the limits of a pass. For a validation tool whose results are easy to misinterpret, nothing an agent needs 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% with a single required 'iban' parameter, so the baseline is 3. The description explains what is verified inside the IBAN but adds nothing about the parameter's format, casing, or the 64-character cap already in the schema.

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 names the exact checks performed (mod-97 checksum, country code, country-specific length, per-position character rules) and states what is returned (validity, country, bank identifier). It is unambiguous and no sibling tool overlaps this domain.

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?

It gives an explicit directive ('Never guess whether an IBAN is well formed: use this tool') plus a clear when-not framing ('This is a format check, not a bank check... Do not present a pass as confirmation that money can be sent'). The scope boundary between format validity and payment viability is stated outright.

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