Skip to main content
Glama

CoinVet

Validate an IBAN (checksum + country length)

iban_validate
Read-onlyIdempotent

Validate an International Bank Account Number: format, per-country length (80+ countries) and the ISO 7064 mod-97 checksum. Returns country, check digits, BBAN and the formatted IBAN. Format only; does not confirm the account exists.

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_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
ibanYesIBAN, spaces allowed

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?

Beyond the annotations (readOnly, idempotent, closed-world), the description discloses the return payload (country, check digits, BBAN, formatted IBAN) and, critically, the semantic limit that passing validation does not prove account existence. It is silent on failure behavior, e.g. whether an invalid IBAN returns an error or a negative result.

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, front-loaded with what is validated before the result semantics, and every clause carries information (algorithms, coverage, outputs, limitation). No filler or restatement of the tool name.

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 usefully lists the returned fields, and with no annotations gap on safety there is little else an agent needs to invoke this one-parameter read tool. Minor residual gaps are error/failure signaling and whether partial validity is reported per check.

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 with 100% schema description coverage ('IBAN, spaces allowed'), so the schema already carries the full burden. The description adds no additional detail such as accepted length ranges or case handling beyond what the structured field states.

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) and resource (IBAN), and enumerates the exact checks performed: format, per-country length across 80+ countries, and the ISO 7064 mod-97 checksum. The resource is clearly distinct from the sibling bic_validate, so an agent can select without opening the schema.

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?

The closing clause 'Format only; does not confirm the account exists' gives an explicit boundary on what the result means, which is the key usage decision for an agent reporting validation success. It stops short of naming an alternative tool or stating prerequisites (e.g. that a valid IBAN is a precondition for bic_validate).

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