Skip to main content
Glama

Check payment details (IBAN and BIC)

check_payment_details
Read-onlyIdempotent

Use when an IBAN comes together with a BIC (SWIFT code). For IBANs without a BIC, use check_iban. Checks the IBAN (length for the country per SWIFT IBAN Registry, 89 countries, and check digits) and the BIC (format, 8 or 11 characters; BIC country against the IBAN country; the bank behind the BIC where GLEIF's BIC-to-LEI list has it). Optionally compares the account country with the partner's country (argument partner); without it 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": {
      "iban": "<iban>",
      "bic": "<bic>"
    },
    "name": "check_payment_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicYesThe BIC (SWIFT code), 8 or 11 characters, e.g. DEUTDEFF or UBSWCHZH80A. Required here; without a BIC use check_iban.
ibanYesThe IBAN, 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. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / bic / description
      Previous value: -"Optional: the BIC (SWIFT code), 8 or 11 characters, e.g. DEUTDEFF or UBSWCHZH80A."New value: +"The BIC (SWIFT code), 8 or 11 characters, e.g. DEUTDEFF or UBSWCHZH80A. Required here; without a BIC use check_iban."
    • addedInput schema / properties / bic / minLength
      Added 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"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "iban"
      -]New value: +[
      +  "iban",
      +  "bic"
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description enumerates what is actually verified (country-specific length per the SWIFT IBAN Registry across 89 countries, check digits, BIC format 8/11 chars, BIC-vs-IBAN country, bank lookup via GLEIF's BIC-to-LEI list) and explicitly bounds the tool with "It cannot verify who owns the account." It does not cover error behavior or output shape, keeping it short of a 5.

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?

The guidance is front-loaded in the first two sentences and every clause carries information (scope, checks, limitation). The parenthetical enumerations are dense but relevant; nothing is filler.

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 still tells the agent what the check covers and what the result signals for the optional partner comparison, plus an explicit capability limit. Minor gap: it does not describe the structure of the returned details (e.g. individual check outcomes).

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 already 100%, so the baseline is 3, but the description adds real meaning for `partner` by explaining that it compares account country with the partner's country and that omitting it yields an explicit "no comparison made" result — a behavioral consequence not present in 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 gives a specific verb (checks) plus both resources (IBAN and BIC) and immediately names the sibling check_iban as the tool for the no-BIC case, so an agent can tell the two apart 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?

It states exactly when to use this tool ("Use when an IBAN comes together with a BIC") and when to use the alternative ("For IBANs without a BIC, use check_iban"), and it flags the optional partner comparison as conditional rather than required.

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