Skip to main content
Glama

generate_uk_bacs_file

Read-onlyIdempotent

Generate UK BACS Standard 18 direct credit or debit files for payroll or supplier payments, with Pay.UK-compliant VOL1/HDR1/UHL1, Contra, and UTL1 records.

Instructions

Generate 100-character UK Pay.UK BACS Standard 18 (VOL1/HDR1/UHL1 + Contra + UTL1) direct credit or debit 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": {
      "service_user_number": "<service_user_number>",
      "originating_company_name": "<originating_company_name>",
      "originating_sort_code": "<originating_sort_code>",
      "originating_account_number": "<originating_account_number>",
      "payments": "<payments>"
    },
    "name": "generate_uk_bacs_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentsYesBACS payment lines.
processing_dateNoProcessing date in YYYY-MM-DD format.
service_user_numberYes6-digit BACS Service User Number (SUN).
originating_sort_codeYes6-digit UK originating Sort Code.
originating_company_nameYesOriginating account or company name (max 18 chars).
originating_account_numberYes8-digit UK originating bank account number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context that output goes through Apify Cloud and is fixed-width 100-character, but says nothing about authentication requirements, timeouts, or what the caller receives back.

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?

A single sentence, front-loaded with the verb and format, and carrying the key spec details with no filler. It is dense with domain jargon, but every clause conveys format or scope 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?

With five required parameters plus a nested payments array and no output schema, the definition should say what the call returns (file bytes, a download URL, an Apify run reference). It also omits the default behavior of the optional processing_date, leaving a meaningful gap for a six-parameter generator.

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%, with every field including nested payment properties documented (SUN, sort codes, amount_pence, transaction codes). The description adds no meaning beyond that, so the baseline of 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?

Specific verb ('Generate') plus a precise resource: 100-character UK Pay.UK BACS Standard 18 direct credit or debit files, including the record types emitted (VOL1/HDR1/UHL1 + Contra + UTL1). This clearly separates it from the sibling generators for ABA, CPA005, NACHA, SEPA, and DATEV formats.

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 format name: an agent can infer this is for UK BACS payments specifically. However, there is no explicit statement of when to choose this over generate_sepa_xml or a generic generator, and no mention of prerequisites such as an Apify account or credentials.

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