Skip to main content
Glama

BRAINIAC Open Banking & Payment Intelligence

Validate an IBAN

payment-intelligence_iban-validate

Validate IBAN structure and mod-97 checksum using public IBAN Registry lengths, and parse domestic bank/account fields for GB, DE, FR, and NL. Bank legal names are not looked up from a live directory. Price $0.02 USDC. POST /api/v1/payment-intelligence/iban-validate. Unpaid calls return 402 and do not run.

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": "payment-intelligence_iban-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
ibanYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose a meaningful amount: the validation method (public IBAN Registry lengths + mod-97), the limited country parsing coverage, the absence of live bank-name resolution, the $0.02 USDC price, the POST path, and that unpaid calls return 402 without executing. What it omits is the shape of a successful response (validity flag vs. error reason vs. parsed fields), which an agent needs to consume the result.

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?

Front-loaded with the capability, then the scope limitations, then commercial/transport facts — a sensible order with no filler. Four short sentences, each carrying distinct information; only the 402 behavior is stated so tersely that it raises a question about other failure codes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description must cover both behavior and results, and it only half-does the latter: it names the categories of parsed fields without saying what a response actually contains or how an invalid IBAN is reported. For a paid validation call whose result must be interpreted, that is a real gap even though the input side is adequately framed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter carries no description, but `iban` is self-explanatory and the description supplies the semantic frame for it — it is checked against registry lengths and a mod-97 checksum, and domestic fields are parsed for four countries. It does not discuss format expectations (spacing, country-code prefix) or the 5–42 length bound, but for one obvious required param that is a minor gap.

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 specific verb+resource: validate IBAN structure and mod-97 checksum, plus parse domestic bank/account fields for four named countries. The IBAN specificity plus the country scope distinguishes it from the sibling routing-number-validate and from the analytics siblings without needing to open a schema.

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 by the scope caveats ("parse domestic bank/account fields for GB, DE, FR, and NL", "Bank legal names are not looked up from a live directory"), which tell the agent what the tool will not cover. There is no explicit when-to-use statement or named alternative for cases outside those four countries or when a bank name lookup is needed.

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