Skip to main content
Glama

generate_sepa_xml

Read-onlyIdempotent

Generate EPC-compliant ISO 20022 SEPA Credit Transfer or Direct Debit XML files for bank-ready payment batches.

Instructions

Generate 2026 EPC-compliant ISO 20022 SEPA Credit Transfer (pain.001.001.09) or Direct Debit (pain.008.001.08) XML 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": {
      "initiating_party_name": "<initiating_party_name>",
      "initiating_party_iban": "<initiating_party_iban>",
      "transactions": "<transactions>"
    },
    "name": "generate_sepa_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemaNoISO 20022 SEPA XML schema version.pain.001.001.09
transactionsYesPayment transactions to include in the SEPA batch.
execution_dateNoRequested execution date in YYYY-MM-DD format.
initiating_party_bicNoOptional 8- or 11-character SWIFT/BIC code of the originating bank.
initiating_party_ibanYesOriginating SEPA bank account IBAN.
initiating_party_nameYesLegal name of the initiating debtor or creditor organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful context — the 2026 EPC compliance target and that generation happens remotely via Apify Cloud, consistent with the open-world hint — but says nothing about what the caller receives (XML string, file URL, artifact) or any size/transaction-count limits.

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 that conveys format, standard, version, and execution venue with no filler. Every clause carries 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 no output schema, the description should explain the return value for a generator tool — whether the agent gets raw XML, a download link, or a job handle from the Apify cloud run — and it does not. Parameters and safety are otherwise adequately covered by the rich schema and annotations.

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% and every property, including the nested transaction fields, is documented in the schema itself, so the baseline of 3 applies. The description only echoes the schema enum values and adds no formatting or validation nuance beyond them.

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 ("SEPA Credit Transfer or Direct Debit XML files") and pins down the exact schema versions (pain.001.001.09 / pain.008.001.08). Against siblings like generate_uk_bacs_file or generate_nacha_ach_file, the SEPA/ISO 20022 scope makes selection unambiguous.

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?

The description names the two supported payment types but never says when to pick this tool over the other format generators (BACS, ABA, CPA005, NACHA) or what prerequisites apply (IBAN validity, execution-date rules). The pain.001 vs pain.008 choice is left entirely to the schema enum.

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