Skip to main content
Glama

iban

Validate international bank account numbers using ISO 13616 mod-97 checksums and country-specific length rules; returns a normalized account number, country, and BBAN.

Instructions

IBAN validation (ISO 13616 mod-97 checksum + per-country length), returns normalised IBAN, country and BBAN. Costs 0.001 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": "iban"
  }
}

Input Schema

NameRequiredDescriptionDefault
ibanYesiban

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the validation algorithm, the pricing model (0.001 USDC on Base per successful call), and the x402 payment-challenge failure mode. It does not say what happens on an invalid IBAN (error vs. a 'valid: false' payload) or whether calls are read-only/idempotent, which keeps it short of a 5.

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?

Three tight sentences, front-loaded with what the tool does, then output, then cost and payment precondition. No filler and no repetition of the schema.

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?

For a single-parameter, read-only validator with no output schema, the description covers purpose, algorithm, return values, and payment requirements. The remaining gap is failure semantics for an invalid IBAN, which an agent would reasonably want before calling.

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?

Only one parameter exists and schema coverage is 100%, so baseline is 3. The description does add modest value by implying the input need not be normalised (it returns a normalised IBAN), but it doesn't state accepted formats such as spaces, lowercase, or country prefixes.

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 (IBAN validation) plus the exact method used (ISO 13616 mod-97 checksum and per-country length), and names the return fields (normalised IBAN, country, BBAN). This clearly separates it from sibling identifier validators such as eu_vat, ch_uid, or lei_lookup.

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 tool's name and scope rather than stated: an agent infers it should call this when checking an IBAN. The description does add a practical precondition — a payment key is needed or the call returns a 402 challenge — but gives no explicit when-not guidance or routing to alternative validators.

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