Skip to main content
Glama

FinOps Studio Zero-Auth Bank Validator & 2-Row Taste-Test MCP

validate_global_bank_identifiers

Deterministically validate IBAN (ISO 13616 MOD-97), SWIFT BIC, US ABA routing (MOD-10), UK Sort Code + Account Number, Australian BSB, Canadian CPA-005 routing, and EU VAT IDs.

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

Input Schema

NameRequiredDescriptionDefault
qNoOptional single identifier to auto-detect
abaNo
bicNo
ibanNo
auBsbNo
vatIdNo
caTransitNo
ukSortCodeNo
caInstitutionNo
ukAccountNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does deliver one meaningful behavioral claim: validation is 'deterministic' and algorithm-specified (MOD-97, MOD-10, CPA-005), which signals pure checksum/format checking with no network lookup or registry existence check. It omits whether the call has any side effects, what it returns, and whether results are reported per field or aggregated.

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 filler; the enumerated standards are all load-bearing. It is slightly dense as a run-on list, but every clause adds information an agent needs.

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?

For a 10-parameter, zero-required tool with no annotations and no output schema, the description leaves the two most consequential questions unanswered: how to choose between 'q' and typed fields, and what the response contains. The format taxonomy is present, but the calling contract is not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 10% — only 'q' is documented — and the description supplies no per-parameter meaning, format examples, or validation rules for the nine undocumented fields. It also omits the crucial coupling requirements implied by its own list, namely that UK Sort Code needs ukAccountNumber and Canadian CPA-005 needs both caTransit and caInstitution, so an agent could easily call with half a pair.

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 ('validate') plus a specific resource class ('global bank identifiers'), then enumerates the exact standards covered (IBAN ISO 13616 MOD-97, SWIFT BIC, ABA MOD-10, UK Sort Code, AU BSB, CA CPA-005, EU VAT). This is unmistakably distinct from the sibling preview_* tools, which parse statement/XML/CSV files.

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, when-not-to-use, or alternative guidance at all. Critically, it never says whether to pass a single value via 'q' for auto-detection or populate the typed per-format fields, nor what happens if both are supplied — the agent must infer the operating mode from the bare schema.

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.