Skip to main content
Glama

BRAINIAC Bank Account Identifiers & Payment Files

Validate a NACHA ACH file

bank-payments_nacha-file-validate
Read-onlyIdempotent

Validate NACHA record order, lengths, ABA checksums, batch/file hashes and totals, reporting every structural error by line. Price $0.03 USDC. POST /api/v1/bank-payments/nacha-file-validate. An unpaid call returns the x402 payment terms and does not run.

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": "<file>"
    },
    "name": "bank-payments_nacha-file-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesfile, string, length 94 to 5000000. Required.
maxErrorsNomaxErrors, integer, from 1 to 1000. Required.

Output Schema

NameRequiredDescriptionDefault
validNovalid. Boolean.
errorsNoerrors. Array.
sourcesNosources. Array.
summaryNosummary. Object.
warningsNowarnings. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 open-world, so the safety profile is covered; the description goes beyond them with concrete operational facts: a $0.03 USDC price and the x402 gate where an unpaid call returns payment terms and does not execute. It also discloses that errors are reported per line, though it stops short of saying whether validation aborts early or how the result is bounded by maxErrors.

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-loads the purpose and checks in one dense sentence, then tacking cost, endpoint, and payment behavior after. No filler, though the endpoint path partially duplicates the tool name and the payment sentence could be tighter.

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

Completeness5/5

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

An output schema exists, so return-shape explanation is unnecessary; what an agent still needs to call this correctly — what is validated, the cost, and the failure mode when unpaid — is all present. Nothing material is missing for a two-parameter read-only validator.

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%, so both 'file' and 'maxErrors' are already documented with types and bounds. The description adds no syntax, encoding, or truncation semantics for either parameter, so the 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?

States a specific verb and resource ('Validate NACHA ... file') and enumerates exactly which checks are performed: record order, lengths, ABA checksums, batch/file hashes and totals. This makes it trivially distinguishable from the sibling nacha-file-build, which produces files rather than checking them.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the pre-submission check for a file, but the description never says when to reach for it over alternatives or what a caller should do when validation fails. The payment prerequisite is disclosed, which is the strongest guidance signal present.

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.

Resources