Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_compliance_iban_bic_validator

Validate IBAN mod-97 checks and country length plus BIC/SWIFT format to catch payment data errors before transactions.

Instructions

[Compliance & Trust] Validate IBAN (mod-97, country length) and BIC/SWIFT format Measured p50 12 ms, p95 16 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://compliance.caelaralabs.com.

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": "caelara_compliance_iban_bic_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicNoBIC/SWIFT code
ibanNoIBAN

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load; it does disclose the validation method (mod-97 checksum plus country-specific length) and measured latency, which is genuine behavioral context. However, it never states what a call returns (boolean verdict vs. error), how invalid input is reported, or whether BIC is cross-checked against the IBAN's country.

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 sentence is front-loaded with a category tag, then purpose, then performance and endpoint, with no filler wording. The benchmark timestamp and URL are arguably marginal but compact.

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

Completeness3/5

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

For a simple two-parameter validator with no output schema, the missing pieces are the return contract, error semantics, and the at-least-one-parameter rule. Everything else an agent needs in order to call the tool is present.

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 coverage is 100%, so the baseline is 3; the description adds the mod-97/country-length rules for IBAN and 'format' for BIC, but not enough to rise above baseline. It omits the either/or/both cardinality implied by zero required parameters.

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 names a specific verb ('Validate') and two specific resources (IBAN and BIC/SWIFT format), and even states the validation techniques (mod-97, country length), so an agent can tell it apart from siblings like vat_ein_checkdigit or crypto_address_checksum_validator. It does not explicitly name a neighboring tool it is not, 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 Guidelines2/5

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

There is no guidance on when to use this versus alternatives, no prerequisites, and no exclusions. It is also silent on the fact that both parameters are optional, so it never says whether one, the other, or both must be supplied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools