Skip to main content
Glama

BRAINIAC Bank Account Identifiers & Payment Files

Build a NACHA ACH file

bank-payments_nacha-file-build
Read-onlyIdempotent

Generate a 94-character NACHA ACH file (PPD/CCD/WEB/TEL) with batch hashes, totals and blocking-factor padding from JSON entries. Price $0.04 USDC. POST /api/v1/bank-payments/nacha-file-build. 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": {
      "immediateDestination": "<immediateDestination>",
      "immediateOrigin": "<immediateOrigin>",
      "destinationName": "<destinationName>",
      "originName": "<originName>",
      "fileCreationDate": "<fileCreationDate>",
      "fileCreationTime": "<fileCreationTime>",
      "batches": "<batches>"
    },
    "name": "bank-payments_nacha-file-build"
  }
}

Input Schema

NameRequiredDescriptionDefault
batchesYesbatches, array. Required.
originNameYesoriginName, string, length 1 to 23. Required.
fileIdModifierNofileIdModifier, string. Required.A
destinationNameYesdestinationName, string, length 1 to 23. Required.
immediateOriginYesimmediateOrigin, string, length 9 to 10. Required.
fileCreationDateYesfileCreationDate, string. Required.
fileCreationTimeYesfileCreationTime, string. Required.
immediateDestinationYesimmediateDestination, string, length 9 to 10. Required.

Output Schema

NameRequiredDescriptionDefault
fileNofile. String.
sourcesNosources. Array.
warningsNowarnings. Array.
entryHashNoentryHash. String.
lineCountNolineCount. Number.
batchCountNobatchCount. Number.
totalDebitNototalDebit. Number.
limitationsNolimitations. Array.
totalCreditNototalCredit. Number.
entryAddendaCountNoentryAddendaCount. Number.
serviceClassCodesNoserviceClassCodes. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely new behavior: the exact output format (94-char records, hashes, totals, blocking-factor padding), a $0.04 USDC cost, the HTTP endpoint, and the x402 payment gate on unauthenticated calls. It stops short of stating response shape or failure modes, but against existing annotations this is solid added context.

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?

Three tight sentences: capability first, then price, then endpoint and payment gate. The raw endpoint path is mildly redundant with the tool name, but nothing is padded or buried.

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 complex nested batch/entry tool, the description is adequate because a full output schema and 100% field-level schema documentation exist, and the payment precondition is explicitly stated. What remains missing is domain guidance on batch/entry grouping semantics or common validation pitfalls before calling.

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 the schema documents every field including lengths, patterns and enums. The description only echoes supported SEC codes (PPD/CCD/WEB/TEL) and the JSON-entries input shape, adding marginal meaning beyond the schema — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: 'Generate a 94-character NACHA ACH file (PPD/CCD/WEB/TEL)' from JSON entries, plus the exact output characteristics (batch hashes, totals, blocking-factor padding). This is clearly distinct from the sibling validate tool, though it never names that sibling as the alternative for checking an existing file.

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 by the action (build a file from entry data) and a real precondition is disclosed: an unpaid call returns x402 payment terms and does not run. However, there is no explicit when-to-use vs when-not guidance and no routing to nacha-file-validate for the checking step.

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