Skip to main content
Glama

generate_canada_cpa005_file

Read-onlyIdempotent

Generate 1,464-byte Payments Canada Standard 005 (CPA-005) EFT files for direct deposits and supplier payments, producing bank-ready Canadian payment batches from transaction data.

Instructions

Generate 1,464-byte Payments Canada Standard 005 (CPA-005) EFT direct deposit and supplier files 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": {
      "originator_id": "<originator_id>",
      "originator_short_name": "<originator_short_name>",
      "transactions": "<transactions>"
    },
    "name": "generate_canada_cpa005_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
transactionsYesCanadian EFT direct deposit or supplier payment items.
originator_idYes10-character Payments Canada Originator ID.
originator_long_nameNoOriginator full name (max 30 chars).
originator_short_nameYesOriginator short name (max 15 chars).
destination_data_centreNo5-digit destination bank data centre code.

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?

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description's main added value is the fixed 1,464-byte record length and the 'via Apify Cloud' remote-execution note, which corroborates openWorldHint. It does not say what is produced or returned (raw file payload, download URL, base64), whether transaction data is validated before emission, or what happens on invalid institution/transit numbers.

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 tightly written sentence that front-loads the format identity and byte length; no filler, no restatement of the title.

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?

With no output schema, the description should have said what the caller receives from a file-generation tool, since the deliverable is the whole point. It also omits any mention of validation or failure behavior, so for a generator of a strict fixed-width banking format the description is adequate but leaves the agent guessing about the result.

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% — every parameter and every nested transaction field is documented inline with constraints and a default — so the schema already carries the semantics. The description only hints at the payment-type distinction through 'direct deposit and supplier', adding nothing about originator_id length or data-centre codes beyond what the schema states.

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?

Uses a specific verb (Generate) plus the exact artifact (1,464-byte Payments Canada Standard 005 / CPA-005 EFT direct deposit and supplier file), so an agent can distinguish it from the ABA, NACHA, BACS or SEPA siblings by format name alone without opening any schema.

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 only implied by the phrase 'Canadian EFT direct deposit and supplier files' — an agent can infer this is the tool for Canada where generate_nacha_ach_file is for the US, but the description never states when to choose it, when not to, or any prerequisites such as needing a valid Payments Canada Originator ID.

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