Skip to main content
Glama

Check an IBAN

check_iban
Read-only

Validate an IBAN's country code, length, format and check digits for any of the 89 IBAN countries, and name the bank behind its bank code (name, BIC, head office) where the directory has it. A valid IBAN doesn't prove the account exists or belongs to the payee; confirm the account holder's name before paying.

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": {
      "iban": "<iban>"
    },
    "name": "check_iban"
  }
}

Input Schema

NameRequiredDescriptionDefault
ibanYesThe IBAN, with or without spaces

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description is not needed to establish safety. It nonetheless adds genuine behavioral context beyond them: validation covers four distinct facets, bank-directory enrichment is best-effort ('where the directory has it'), and validity is explicitly scoped to syntax/checksum rather than account existence — a caveat an agent would otherwise have to guess.

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?

Two sentences, no filler: the first states capability and enrichment, the second states the critical limitation and the action it implies. The most decision-relevant content is front-loaded.

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 carries the burden of describing returns, and it does — enumerating the validated facets and the bank fields (name, BIC, head office). What is left unspecified is the shape of a failed validation (error vs. flag field), a minor gap for a one-parameter read tool.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains the input type. The description adds no syntax or formatting guidance for the iban field, and the useful detail that spaces are accepted lives only in the schema — baseline 3 applies when the schema does the heavy lifting.

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?

Names a specific verb (validate) plus the exact facets checked (country code, length, format, check digits), the scope (89 IBAN countries), and a secondary output (bank name, BIC, head office). An agent knows precisely what this tool does without opening the schema, and none of the siblings (stablecoin_rate, payment_holidays, etc.) overlap with it.

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?

Implies the use case clearly (verifying an IBAN before paying) and adds an explicit boundary condition: a valid IBAN does not prove the account exists or belongs to the payee, so confirm the account holder name before paying. No alternative sibling tool is named, but none of the listed siblings is a substitute for IBAN validation, so the omission is not costly.

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