Skip to main content
Glama

generate_australian_aba_file

Read-onlyIdempotent

Creates Australian AusPayNet BECS Direct Entry (.aba) files with 120-character records and Record 7 hash/net balancing for bank-ready batch payments.

Instructions

Generate 120-character Australian AusPayNet BECS Direct Entry (.aba / Cemtex) files with Record 7 hash/net balancing 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": {
      "bsb": "<bsb>",
      "account_number": "<account_number>",
      "user_name": "<user_name>",
      "apca_user_id": "<apca_user_id>",
      "transactions": "<transactions>"
    },
    "name": "generate_australian_aba_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
bsbYesOriginating or trace Australian 6-digit BSB (XXX-XXX).
user_nameYesOriginating user preferred name (max 26 chars).
descriptionNoBatch entry description (max 12 chars, e.g., PAYROLL).
apca_user_idYes6-digit AusPayNet / APCA User Identification Number.
transactionsYesAustralian Direct Entry detail lines (Type 1 records).
account_numberYesOriginating or trace bank account number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 behavior, so the safety profile is covered. The description adds genuinely useful context in 'via Apify Cloud' (an external service dependency) and the Record 7 balancing behavior, but says nothing about how the generated file is returned (inline, base64, URL, or written to disk) — a material omission for a file-producing tool with no output schema.

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 dense sentence with the key technical qualifiers (character width, standard, Record 7 balancing, cloud dependency) front-loaded and no filler. Nothing could be cut 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?

Six parameters with full schema coverage and strong annotations mean the input side is well served. However, for a file-generation tool with no output schema, the definition never explains what the caller receives back or how the .aba file is delivered, which leaves a real 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%, including per-field hints on BSB format, APCA user ID, transaction codes, and character limits, so the schema carries the parameter burden. The description adds nothing beyond it — 'Record 7 hash/net balancing' relates to output rather than inputs. Baseline 3 applies.

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?

States a specific verb and resource: 'Generate 120-character Australian AusPayNet BECS Direct Entry (.aba / Cemtex) files with Record 7 hash/net balancing'. The standard and format specificity effectively separates it from the Canadian, NACHA, and BACS siblings, though it never names an alternative explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. An agent gets no statement about when to reach for this versus validate_bank_routing or audit_bank_file_format, nor any precondition such as required registration with AusPayNet.

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