Skip to main content
Glama

IBAN and BIC validator

submit_iban_bic_validator
Idempotent

Validate IBAN checksums and BIC formats across a table of accounts. Before a payment run, to catch malformed account identifiers. Do not choose this when account existence must be confirmed, which needs the bank. Example requests: Validate these IBANs and BICs. | Which of these account numbers are wrong? | Check the checksums on this IBAN list.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_iban_bic_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

The description adds real behavioural context beyond the annotations by stating the validation boundary: it checks checksums and formats only, not whether the account exists. However, it omits that this is a priced, quote-authorized job submission (readOnlyHint=false, quote_id/accepted_price in the schema), leaving the agent to discover pricing and authorization behaviour from structured fields alone.

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 purpose and the exclusion are front-loaded in the first two sentences, with examples appended as supporting material. The example-request list is somewhat padded but is functional for routing; nothing else is wasted.

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 an output schema, annotations, and a 75%-covered nested input schema, the description only needs to supply purpose and boundaries, which it does. The one gap is the absence of any mention that submission is a priced job requiring a quote and an authorizer, which an agent would otherwise have to infer from parameter names.

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 75%, so the schema already explains the ibans CSV payload, quote_id, and authorized_by. The description adds no parameter-level meaning — it never mentions the CSV shape, the quote/price mechanism, or the authorizing identifier — so it sits at the baseline for a well-documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource pair ('Validate IBAN checksums and BIC formats across a table of accounts') and scopes it to a table of accounts, which is enough to separate it from single-value validators. It does not explicitly differentiate from near neighbours such as submit_sepa_payment_file_builder or submit_iso20022_validator, which also touch payment identifiers, so it falls short of a 5.

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 gives an explicit when ('Before a payment run, to catch malformed account identifiers') and an explicit when-not ('Do not choose this when account existence must be confirmed, which needs the bank'). The three example requests further anchor the routing decision for an agent choosing among many submit_* siblings.

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