Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

SWIFT code, BIC validation: structure, country and branch

bic_validate
Read-only

Check a BIC (SWIFT code) against the ISO 9362 structure: institution code, a real country code with its name, location code, branch code, whether it is the head office (XXX or 8 characters), a test BIC or a passive participant, and the 11-character form. Computed locally; it checks the format and country, not whether the bank exists. Use before an international transfer or to clean payment data; for account numbers use validate_iban. Example: bic=DEUTDEFF500. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "bic": "<bic>"
    },
    "name": "bic_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicYesBIC / SWIFT code, 8 or 11 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, closed-world and non-destructive behavior, and the description adds genuinely useful context beyond them: computation is local, results are not a proof of bank existence, and pricing/rate behavior is spelled out ($0.01/call, 25 free, failed calls free, repeats charged — consistent with idempotentHint=false). It does not describe latency or the shape of the failure response, but the economic and safety profile is well disclosed.

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?

Front-loaded with the validation scope, then usage, then example, then pricing — a sensible ordering with no filler. The first sentence is long and enumerative, and the closing pricing sentence packs several clauses, but every claim carries information an agent needs.

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 takes on the burden of conveying results, and it names the validated components (institution, country name, location, branch, head office, test/passive flags) well enough for an agent to anticipate the response. It stops short of saying explicitly which of those are returned versus merely checked, which is the only remaining gap for a one-parameter tool.

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% and the single parameter is already documented as an 8- or 11-character string, so the schema does most of the work. The description still adds value by giving a concrete example (bic=DEUTDEFF500) and by explaining why both lengths matter (11-character form, head-office XXX/8-character case).

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 (check a BIC/SWIFT code) plus the exact standard applied (ISO 9362 structure) and enumerates what is examined: institution code, country, location code, branch, head-office flag, test BIC, passive participant, 11-character form. It also names the sibling it is not (validate_iban), so an agent can separate it from the other validators.

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 explicit when-to-use contexts (before an international transfer, cleaning payment data) and an explicit alternative with its condition (account numbers → validate_iban). It also states the boundary of the check — format and country only, not whether the bank exists — which prevents over-trusting the result.

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.