Skip to main content
Glama

BRAINIAC Bank Account Identifiers & Payment Files

Build an IBAN from a BBAN

bank-payments_iban-from-bban
Read-onlyIdempotent

Compute ISO 13616 check digits for a country code and domestic BBAN, then validate the resulting IBAN structure. Price $0.01 USDC. POST /api/v1/bank-payments/iban-from-bban. An unpaid call returns the x402 payment terms and does 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": {
      "country": "<country>",
      "bban": "<bban>"
    },
    "name": "bank-payments_iban-from-bban"
  }
}

Input Schema

NameRequiredDescriptionDefault
bbanYesbban, string, length 1 to 34. Required.
countryYescountry, string. Required.

Output Schema

NameRequiredDescriptionDefault
ibanNoiban. String.
validNovalid. Boolean.
sourcesNosources. Array.
ibanPrintNoibanPrint. String.
checkDigitsNocheckDigits. String.
limitationsNolimitations. Array.
expectedBbanLengthNoexpectedBbanLength. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds important payment context: the $0.01 USDC price, the POST endpoint, and that an unpaid call returns x402 payment terms without running. That is useful behavioral disclosure beyond the annotations.

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?

The description is front-loaded with the core operation and then adds payment and endpoint details. Each sentence contributes useful information, with no redundant or filler wording.

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

Completeness5/5

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

This is a simple two-parameter tool with an output schema and rich annotations. The description covers the core computation, the payment gate, and the endpoint behavior, which is sufficient for an agent to call it correctly.

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 description coverage is 100%, so the schema already documents both parameters adequately. The description restates that it takes a country code and domestic BBAN but does not add examples, formatting rules, or other meaning beyond the schema.

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?

The description states a specific verb and resource: compute ISO 13616 check digits from a country code and domestic BBAN, then validate the resulting IBAN structure. This makes the transformation and validation behavior clear without relying on the title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool does but gives no explicit when-to-use or when-not-to-use guidance. It also does not route the agent toward or away from any alternative, including the sibling validation tools.

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