Skip to main content
Glama

SEPA XML Generator - pain.001 credit transfer + pain.008 direct debit

sepa_xml
Read-onlyIdempotent

Turn a payment list (JSON rows or CSV) into a bank-ready SEPA XML file: credit transfer pain.001 or direct debit pain.008 (versions 2009 to 2019), validated against the official XSD, IBAN and creditor-ID checks, next TARGET2 business day, rejected rows listed with the reason. Also mode=check (validate an existing SEPA file) and mode=upgrade (old pain version -> current). Runs on our server, nothing stored. Free: 25 calls/day per IP. Paid: $0.01 per call via x402 at https://radarbg.com/x402/sepa-xml.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "iban": "DE89370400440532013000",
      "name": "Example GmbH",
      "rows": [
        {
          "iban": "DE02120300000000202051",
          "name": "Max Muster",
          "amount": "125.50",
          "reference": "Invoice 2026-001"
        }
      ],
      "type": "credit_transfer"
    },
    "name": "sepa_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicNoYour BIC (optional)
csvNoOr the payment list as CSV text with a header line
xmlNoSEPA XML text for mode check / upgrade
ibanNoYour IBAN
modeNogenerate, check, upgrade or templategenerate
nameNoYour company name (payer for transfers, creditor for debits)
rowsNoPayments: name, iban, amount, reference (+ bic, mandate_id, mandate_date for debits)
typeNocredit_transfer or direct_debitcredit_transfer
creditor_idNoSEPA creditor identifier (direct debit only)
execution_dateNoYYYY-MM-DD (default: next business day)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: official XSD validation, IBAN and creditor-ID checks, TARGET2 next-business-day defaulting, rejected rows returned with reasons, server-side execution with nothing stored, and explicit limits (25 calls/day free, $0.01/call via x402). This is a generator that writes no state, so readOnlyHint=true is consistent, not contradicted. Only the response shape (inline XML vs. a link) is left undisclosed.

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?

Front-loaded with the core purpose in the first clause, then modes, then pricing/limits, with an explicit 'Also mode=...' marker to separate secondary paths. The pricing sentence is dense but operationally relevant; the paragraph is packed but not padded.

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

Completeness4/5

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

With 10 optional parameters and no output schema, the description still covers the generation contract, validation behavior, error reporting, and cost model. The one real gap is what the caller receives (raw XML string, file download, or URL), which matters because no output schema exists to answer it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real linkage not evident from the schema alone: rows/CSV are the generation inputs while xml belongs to check/upgrade, creditor_id applies only to direct debit, and execution_date defaults to the next TARGET2 business day. That mapping meaningfully reduces mis-invocation risk.

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 concrete verb and resource chain: turn a payment list into a SEPA XML file, specifically pain.001 credit transfer or pain.008 direct debit, versions 2009-2019. It also names the alternate modes (check, upgrade) and the input forms (JSON rows or CSV), so an agent can tell it apart from siblings like iban_validator or data_convert without opening the schema.

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

Usage Guidelines4/5

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

Gives clear context for each mode: mode=check validates an existing SEPA file, mode=upgrade converts an old pain version to the current one, and the default path generates from rows/CSV/JSON. It does not explicitly say when NOT to use this tool or point at a sibling (e.g. iban_validator for a single IBAN check), so it stops short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources