Skip to main content
Glama

Caelara Labs Compliance & Trust

iban_bic_validator

Validate IBAN (mod-97, country length) and BIC/SWIFT format

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "iban_bic_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicNoBIC/SWIFT code
ibanNoIBAN

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses the validation rules (mod-97 checksum, country-specific length), which is genuinely useful, but says nothing about what happens on failure (error vs. boolean), whether both fields are optional, what occurs if neither is passed, or whether the call is side-effect free.

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?

A single front-loaded sentence with no wasted words; the parenthetical efficiently packs in the two validation rules. It is perhaps too terse for the behavior it needs to convey, but nothing is redundant.

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

Completeness2/5

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

With no output schema and no annotations, the description should explain what a validation result looks like and how the optional-field case behaves; it explains neither. For a validation tool the agent cannot predict the response shape or failure semantics from this definition alone.

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 two parameters are already documented as 'IBAN' and 'BIC/SWIFT code'. The description adds only the validation standard applied, not parameter-specific semantics such as accepted formatting (spaces, lowercase) or length expectations. Baseline 3 is appropriate.

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?

States a specific verb (validate) and the two resources (IBAN and BIC/SWIFT), and even names the validation method (mod-97, country length). An agent can tell exactly what the tool does, though nothing differentiates it from the other check-digit/composite tools in the catalog.

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?

There is no when-to-use guidance, no mention of alternatives such as vat_ein_checkdigit or the composite KYB tools, and no prerequisites. Usage is only implied by the tool name and verb.

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