Skip to main content
Glama

validate_bank_routing

Read-onlyIdempotent

Validate standalone bank routing identifiers such as IBAN, ABA, UK sort code, and Australian BSB with offline checksum rules to catch payment errors early.

Instructions

Offline deterministic validator for standalone bank routing identifiers: ISO 13616 IBAN (MOD-97), US 9-digit ABA routing number (MOD-10), UK 6-digit BACS Sort Code, and Australian 6-digit BSB. Use for standalone bank identifiers; to inspect a full multi-line payment or statement file, use audit_bank_file_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": "validate_bank_routing"
  }
}

Input Schema

NameRequiredDescriptionDefault
ibanNoInternational Bank Account Number to verify via ISO 13616 MOD-97 (e.g., DE89370400440532013000).
au_bsbNoAustralian 6-digit BECS BSB number to validate and normalize (e.g., 062-000).
uk_sort_codeNoUK 6-digit BACS Sort Code to validate and normalize (e.g., 40-05-15).
aba_routing_numberNoUS 9-digit ABA Fedwire/ACH routing number to verify via MOD-10 checksum (e.g., 021000021).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that with 'offline deterministic', telling the agent there is no network dependency and results are reproducible, plus naming the checksum algorithms used. However, it never says what a validation produces (pass/fail shape, normalization of the sort code/BSB), and with no output schema that is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the capability and ending with the disambiguation rule. Every clause carries information; nothing is repeated for filler.

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?

For a four-optional-parameter, read-only validator the coverage is nearly complete: formats, algorithms, examples, and the sibling boundary are all present. The remaining shortfall is the absence of any statement about return values or how multiple supplied identifiers are handled, which matters because there is no output schema to fill that gap.

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%, and each parameter already documents its format, example, and algorithm, so the schema carries the burden. The description only restates the same four formats and checksums, adding no new semantics such as mutual exclusivity or whether one, several, or all parameters may be supplied. Baseline 3 applies.

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?

The description gives a specific verb and resource ('Offline deterministic validator for standalone bank routing identifiers') and enumerates exactly which identifier formats and algorithms are covered (ISO 13616 IBAN MOD-97, ABA MOD-10, UK BACS Sort Code, Australian BSB). It explicitly contrasts itself with the sibling audit_bank_file_format, so an agent can route between them without opening either schema.

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 states both the when ('standalone bank identifiers') and the when-not plus alternative ('to inspect a full multi-line payment or statement file, use audit_bank_file_format'). This is an explicit routing rule, not an implied one.

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