Skip to main content
Glama

verify_iban

Read-onlyIdempotent

Check an IBAN’s country length, available national format rules and Mod-97 checksum on the EuroKYB server. Returns valid and reason. This checks the identifier only. Account ownership and existence require confirmation from the bank.

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 with its country prefix. Spaces and lowercase are accepted, e.g. GB82 WEST 1234 5698 7654 32.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / iban / description
      Previous value: -"IBAN string"New value: +"IBAN with its country prefix. Spaces and lowercase are accepted, e.g. GB82 WEST 1234 5698 7654 32."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds value by disclosing the return fields (valid and reason) and the guarantee limits, which no structured field provides. It stops short of covering authentication, rate limits, or what the failure reasons look like, so a 3 rather than a 4.

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 short sentences, front-loaded with what is checked, then the return shape, then the caveat. Every sentence carries distinct information and nothing is repeated from the name or title.

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-parameter validation tool with no output schema, the description is nearly self-sufficient: it names the checks, the return fields, and the ownership caveat. The only minor gap is that it does not indicate how 'reason' behaves on failure or whether the call is remote-slow.

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% and the single iban parameter is already documented with format acceptance (spaces, lowercase, example). The description adds no further parameter meaning beyond what the schema states, so this lands at the baseline.

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 (check) and resource (IBAN) plus the exact rule set applied: country length, national format rules, and the Mod-97 checksum. It also names the execution context (EuroKYB server), so an agent can tell this apart from the VAT, company-KYB, and website-audit siblings without opening 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 Guidelines4/5

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

Draws a clear scope boundary: 'This checks the identifier only. Account ownership and existence require confirmation from the bank.' That is an explicit when-not, telling the agent not to use this result as proof of account existence. It does not name a sibling alternative, but the excluded use case is spelled out rather than implied.

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