Skip to main content
Glama

verify_iban

Validate an international IBAN against ISO 13616 Mod-97 checksum rules to confirm the account identifier is correctly formatted and checksum-valid.

Instructions

Validate an international IBAN using ISO 13616 Mod-97 checksum rules.

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

Input Schema

NameRequiredDescriptionDefault
ibanYesIBAN string

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a meaningful behavioral trait — validation is checksum/structural only per Mod-97, implying it will not verify account existence or bank routing. It omits the result shape (boolean vs. structured error), case/whitespace normalization behavior, and any failure reasons, which an agent needs to interpret output.

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?

A single front-loaded sentence with zero filler. The standard and algorithm are named in the same breath as the action, so nothing needs to be skimmed past.

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 one-string, single-purpose validator this is close to sufficient: the action, the standard, and the checksum algorithm are all present. The remaining gap is the absence of an output schema combined with no mention of what a validation verdict looks like, which leaves the agent guessing at return semantics.

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% for the single required parameter, so baseline is 3. The description adds the standard being applied (ISO 13616 Mod-97), which hints at expected input format, but contributes no detail on accepted formatting, country-prefix handling, or length constraints beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Validate an international IBAN" gives a specific verb plus resource, and naming the ISO 13616 Mod-97 rule makes the scope concrete. It does not need sibling differentiation, since verify_eu_vat_vies and check_czech_company_kyb cover entirely different domains, but it also does not explicitly say what it is not (e.g., that it does not confirm the account exists).

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 only implied: an agent can infer this should be called when it has an IBAN string and needs a format/checksum verdict. There is no statement of when to prefer it over the VAT or KYB siblings, nor any prerequisite (e.g., input must be a complete IBAN, not just a BBAN).

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