Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENNoOptional Apify token for the zero-install local stdio MCP server. The zero-auth preview MCP server requires no token.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
validate_bank_routingA

Offline deterministic validator for standalone bank routing identifiers: ISO 13616 IBAN (MOD-97), US 9-digit ABA routing number (MOD-10), UK 6-digit BACS Sort Code, and Australian 6-digit BSB. Use for standalone bank identifiers; to inspect a full multi-line payment or statement file, use audit_bank_file_format.

audit_bank_file_formatA

Offline pre-flight inspector for multi-line bank, payroll, or statement files: detects format (NACHA 94-char, AU ABA 120-char, UK BACS 100-char, CA CPA-005 1464-byte, Norma 43 80-char, BAI2, SEPA/ISO 20022 XML) and validates every embedded IBAN and ABA checksum. Use for full files; to check a single standalone identifier, use validate_bank_routing.

generate_sepa_xmlA

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.

generate_eu_einvoice_xmlB

Generate EN 16931 EU E-Invoice XML (Peppol BIS 3.0 UBL, German XRechnung 3.0 UBL, or Factur-X/ZUGFeRD 2.3 CII) via Apify Cloud.

generate_nacha_ach_fileA

Generate 94-character Block-10 padded US NACHA ACH (.ach) vendor payment and payroll direct deposit files (CCD, PPD, WEB) via Apify Cloud.

parse_bai2_statementA

Parse corporate BAI2 (.bai / .bai2) cash-management bank statements (records 01, 02, 03, 16, 88, 49, 98, 99) into structured JSON and CSV via Apify Cloud.

generate_datev_csvB

Generate German DATEV EXTF v700 Buchungsstapel CSV (SKR03 / SKR04) accounting import batches via Apify Cloud.

generate_australian_aba_fileB

Generate 120-character Australian AusPayNet BECS Direct Entry (.aba / Cemtex) files with Record 7 hash/net balancing via Apify Cloud.

parse_pain002_status_xmlA

Parse ISO 20022 pain.002 XML bank payment rejection reports (AC04, AM04, BE04, MD01) into plain-English remediation steps via Apify Cloud.

generate_uk_bacs_fileA

Generate 100-character UK Pay.UK BACS Standard 18 (VOL1/HDR1/UHL1 + Contra + UTL1) direct credit or debit files via Apify Cloud.

generate_canada_cpa005_fileA

Generate 1,464-byte Payments Canada Standard 005 (CPA-005) EFT direct deposit and supplier files via Apify Cloud.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 11 tools

Disambiguation5/5

Each tool has a distinct resource-and-action identity: parsers (pain.002, BAI2), validators (routing, file audit), and format-specific generators (SEPA, EU e-invoice, NACHA, DATEV, ABA, BACS, CPA-005). The only plausible overlap — validate_bank_routing vs audit_bank_file_format — is explicitly disambiguated in both descriptions by scope (single identifier vs full file). Country/format generators are separated by unambiguous format names.

Naming Consistency5/5

All names follow a strict snake_case verb_noun pattern: parse_*, validate_*, audit_*, generate_*. Naming is fully predictable, so an agent can infer the verb class and target format from the name alone.

Tool Count5/5

Eleven tools is well within the ideal 3-15 range for a payments/accounting file toolkit. Each tool maps to a distinct, non-redundant format or validation concern, so no tool feels like filler.

Completeness4/5

Generation and validation coverage is broad (SEPA, NACHA, BACS, ABA, CPA-005, DATEV, EN 16931) with inbound parsing for pain.002 and BAI2. Notable gaps remain: no CAMT.053/MT940 bank statement parsing and no structured parsing of inbound NACHA/BACS/ABA return files, though audit_bank_file_format partially covers file inspection.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues