Skip to main content
Glama

audit_bank_file_format

Read-onlyIdempotent

Detect bank, payroll, and statement file formats, then validate every embedded IBAN and ABA checksum to catch payment file errors before processing.

Instructions

Offline pre-flight inspector for multi-line bank, payroll, or statement files: detects format (NACHA 94-char, AU ABA 120-char, UK BACS 100-char, CA CPA-005 1464-byte, Norma 43 80-char, BAI2, SEPA/ISO 20022 XML) and validates every embedded IBAN and ABA checksum. Use for full files; to check a single standalone identifier, use validate_bank_routing.

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": {
      "file_content": "<file_content>"
    },
    "name": "audit_bank_file_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_contentYesRaw text content of the bank payment file, CSV batch, BAI2 statement, or ISO 20022 XML snippet to audit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds that inspection is 'offline' and that checksums are verified across the whole file. It does not describe the result shape (detected format vs. per-record failures) or behavior on malformed/oversized input, which would matter for a validation tool.

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, no filler: the capability and format list come first, the sibling routing second. Every clause carries information an agent needs (char widths, byte length, checksum validation).

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 one-parameter, read-only audit tool with full annotations, this is nearly complete. The remaining gap is return-value behavior—no output schema exists and the description never says whether it returns a detected-format report, a validity boolean, or per-record errors.

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 fully documented, so the baseline is 3. The description adds value by enumerating the concrete payload shapes expected (NACHA/ABA/BACS/CPA-005/Norma 43/BAI2/SEPA XML), telling the agent more about acceptable input than the schema's generic 'bank payment file' wording.

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?

Names a specific verb and object ('Offline pre-flight inspector ... detects format ... validates every embedded IBAN and ABA checksum') and enumerates the exact formats handled (NACHA 94-char, ABA 120-char, BACS 100-char, CPA-005 1464-byte, Norma 43 80-char, BAI2, SEPA XML). That level of specificity clearly separates it from parse_bai2_statement or validate_bank_routing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly scopes usage to 'full files' and routes single-identifier checking to validate_bank_routing, giving a concrete alternative with a triggering condition. It stops short of distinguishing audit from the parse_* siblings, so an agent must still infer when to parse versus pre-flight a BAI2/ISO 20022 payload.

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