Pactus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingB | Health check tool. Returns service metadata. |
| parse_pacs008A | Parse a pacs.008.001.08 (FI-to-FI Customer Credit Transfer) message. pacs.008 is the most common ISO 20022 message in cross-border payments and is required for all SWIFT cross-border traffic from November 2025. Each message carries one or more credit transfer instructions between financial institutions. Returns a structured ParsedPacs008 with the group header (message-level metadata) and a list of transactions (each instruction). On parse or validation failure, returns {"error": "..."} so the agent can explain rather than crashing. |
| parse_pacs002A | Parse a pacs.002.001.10 (FI-to-FI Payment Status Report) message. pacs.002 is the response to a pacs.008 credit transfer. It reports whether each transaction was accepted, rejected, or is in an intermediate state. Each transaction carries a status code and optionally one or more structured reason codes explaining the outcome. Returns a structured ParsedPacs002 on success, or {"error": "..."} on failure. |
| parse_pain001A | Parse a pain.001.001.09 Customer Credit Transfer Initiation message. pain.001 is the initiating message in a credit transfer flow, sent by a corporate or customer to their bank. It carries one or more payment batches (PaymentInformation), each grouping transactions that share a debtor account, execution date, and service level. Returns a structured ParsedPain001 on success, or {"error": "..."} on failure. |
| parse_camt053A | Parse a camt.053.001.08 Bank-to-Customer Cash Management Statement. camt.053 is the structured account statement sent by a bank to its customer. It reports balances (opening, closing, interim) and individual debit/credit entries for a period, each optionally broken down to individual transaction details. It is the primary source for automated bank reconciliation. Returns a structured ParsedCamt053 on success, or {"error": "..."} on failure. |
| validate_pacs008A | Validate a pacs.008.001.08 message against its XSD. Returns a structured ValidationReport listing every XSD violation found, with line/column/path information. Unlike parse_pacs008, this does not stop at the first error — all violations are reported so the user can fix them in one pass. |
| validate_pacs002A | Validate a pacs.002.001.10 message against its XSD. Returns a structured ValidationReport listing every XSD violation found, with line/column/path information. Unlike parse_pacs002, this does not stop at the first error — all violations are reported so the user can fix them in one pass. |
| validate_pain001A | Validate a pain.001.001.09 message against its XSD. Returns a structured ValidationReport listing every XSD violation found, with line/column/path information. Unlike parse_pain001, this does not stop at the first error — all violations are reported so the user can fix them in one pass. |
| validate_camt053A | Validate a camt.053.001.08 message against its XSD. Returns a structured ValidationReport listing every XSD violation found, with line/column/path information. Unlike parse_camt053, this does not stop at the first error — all violations are reported so the user can fix them in one pass. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a specific ISO 20022 message type and action (parse vs validate), with no overlap. The ping tool is uniquely for health checks.
All tools follow a consistent verb_messageType pattern (e.g., parse_pacs008, validate_pacs002). The naming is uniform and predictable.
9 tools cover the essential operations (parse and validate) for four common payment message types. The count is well-scoped for this domain.
The server covers the core parse and validate needs for the most frequent ISO 20022 payment messages. A minor gap is the absence of related messages like camt054 or pacs004, but the current set is sufficient for typical use.