Skip to main content
Glama

generate_nacha_ach_file

Read-onlyIdempotent

Create bank-ready US NACHA ACH files with 94-character Block-10 padding for vendor payments and payroll direct deposits (CCD, PPD, WEB) to submit ACH batches to the network.

Instructions

Generate 94-character Block-10 padded US NACHA ACH (.ach) vendor payment and payroll direct deposit files (CCD, PPD, WEB) via Apify Cloud.

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": {
      "immediate_destination": "<immediate_destination>",
      "company_name": "<company_name>",
      "company_id": "<company_id>",
      "entries": "<entries>"
    },
    "name": "generate_nacha_ach_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesYesACH debit or credit entry detail records.
sec_codeNoStandard Entry Class code (CCD business, PPD payroll/consumer, WEB internet).CCD
company_idYes10-character NACHA Company ID (typically 1 plus 9-digit EIN).
company_nameYesOriginating company name (up to 16 characters).
effective_entry_dateNoSettlement date in YYMMDD or YYYY-MM-DD format.
immediate_destinationYes9-digit US ABA routing number of the originating or destination bank.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/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 safety is covered. The description adds the output format detail (94-char Block-10 padding) and the execution venue ('via Apify Cloud'), which explains the open-world hint, but says nothing about auth/API token needs, size or entry-count limits, or whether the .ach file comes back inline or as a download reference.

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?

A single front-loaded sentence with zero filler: verb, artifact, format constraint, SEC codes, use cases, and runtime venue in that order. Nothing could be removed without losing information.

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

Completeness3/5

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

There is no output schema, so the description carries the burden of explaining what the agent receives — inline file content versus a URL or Apify dataset reference — and it does not. For a generator producing a fixed-width banking artifact, that return-value ambiguity plus unstated entry limits leaves a real gap, though the input side is fully specified.

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 every parameter including nested entry fields is documented in structured form; the description only echoes the SEC code options. Baseline 3 applies since the schema does the semantic heavy lifting and the description adds no format rules, defaults behavior, or date-handling nuance beyond it.

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 (Generate) and resource (US NACHA ACH .ach files) plus the distinctive technical traits: 94-character Block-10 padding and SEC codes CCD/PPD/WEB. This immediately separates it from the country-specific siblings (Australian ABA, Canada CPA005, UK BACS) without needing to name 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?

Use case is implied by 'vendor payment and payroll direct deposit,' which tells an agent the business scenarios, but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as validate_bank_routing or audit_bank_file_format before or after generation.

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