Skip to main content
Glama

Check IBAN

check_iban
Read-onlyIdempotent

Use for one or several IBANs when no BIC is given. With a BIC, use check_payment_details. Offline check of up to 20 IBANs: format, length for the country and check digits. Optionally compares the account's country with the partner's country (argument partner: a country code or the partner's VAT ID) and flags a mismatch as a notice; without partner the result says that no comparison was made. It cannot verify who owns the account.

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": {
      "ibans": "<ibans>"
    },
    "name": "check_iban"
  }
}

Input Schema

NameRequiredDescriptionDefault
ibansYes1 to 20 IBANs, with or without spaces.
partnerNoOptional: the partner's two-letter country code or VAT ID, to compare with the account's country.
with_receiptNoOptional, default false. Set true only when the user asks for a signed receipt of this check for their files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / ibans / items / minLength
      Removed value: -1
    • addedInput schema / properties / with_receipt
      Added value: +{
      +  "description": "Optional, default false. Set true only when the user asks for a signed receipt of this check for their files.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, but the description adds substantial context beyond them: the check is offline, capped at 20 IBANs, limited to format/length/check digits, and a partner mismatch is surfaced as a notice rather than a failure. The explicit limitation 'It cannot verify who owns the account' prevents an agent from overclaiming 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with the routing rule and followed by scope, optional behavior, and limitation. No sentence restates the title or the schema, and each adds a distinct decision-relevant fact.

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?

For a three-parameter, annotation-covered read tool with no output schema, the description covers scope, limits, optional comparison behavior, and the key negative guarantee. An agent has everything needed to call it correctly and to interpret the outcome.

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 100%, so the baseline would be 3, but the description adds real meaning for 'partner' by explaining it accepts a country code or a VAT ID, that a mismatch is reported as a notice, and that omitting it yields an explicit 'no comparison made' result. The 'with_receipt' parameter is left entirely to the schema, which keeps this from a 5.

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 and resource ('Offline check of up to 20 IBANs') and enumerates exactly what is validated: format, country-specific length, and check digits. It also explicitly distinguishes itself from the sibling check_payment_details by the presence or absence of a BIC, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit selection rule: use this when no BIC is given, and use check_payment_details when a BIC is available. It also scopes the optional partner comparison and states what happens without it, so both the when and the when-not are covered.

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