mcp-edi
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_edifactA | Parse a raw UN/EDIFACT interchange into structured JSON: UNA-declared separators, UNB/UNZ envelope, one entry per UNH/UNT message with decomposed segments (composite and simple elements), message type recognition (ORDERS, DESADV, INVOIC, ORDRSP...) and UNT/UNZ counter verification. Returns issues with segment, position, expected and found values. |
| parse_x12A | Parse a raw ANSI X12 interchange into structured JSON. Delimiters are deduced from the ISA segment itself (element separator = 4th character, component separator = ISA16, segment terminator = the character after ISA16). Returns the ISA/GS/ST hierarchy with decomposed segments, transaction type recognition (850, 856, 810, 997...) and SE/GE/IEA counter and control-number verification. |
| parse_cxmlA | Parse a cXML e-procurement document (PunchOutSetupRequest, PunchOutSetupResponse, OrderRequest) into structured JSON: From/To/Sender credentials, punchout session data, order header with totals and addresses, and line items with quantities and prices. SharedSecret values are detected but never echoed. |
| validate_messageA | Detect the EDI standard (EDIFACT, X12 or cXML), verify the envelope structure, the mandatory segments for the recognized message type, and all control counters. Returns an actionable list of errors and warnings — each with segment, position, expected and found — plus a one-line summary. |
| explain_segmentA | Explain an EDI segment tag in plain English: role, key elements and a realistic example. Covers 35 EDIFACT segments (UNB, BGM, DTM, NAD, LIN, QTY...) and 28 X12 segments (ISA, ST, BEG, N1, PO1, HL...). Tags that exist in both standards (DTM, LIN) return both entries unless a standard is specified. |
| generate_edifactA | Generate a syntactically valid EDIFACT ORDERS D.96A interchange (UNA + UNB...UNZ) from a simple JSON order description: parties, dates, currency and line items. Envelopes, escaping and UNT/UNZ counters are computed automatically; the output round-trips through parse_edifact with zero issues. |
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 6 tools
Each tool has a distinct purpose: parsing three different EDI standards, validation, segment explanation, and generation. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with underscores: parse, validate, explain, generate. No mixing of conventions.
Six tools cover the core EDI workflows (parse, validate, explain, generate) for the main standards without being excessive or sparse.
Covers parsing for EDIFACT, X12, and cXML, validation across all, explanation, and generation for EDIFACT. Missing generation for X12 and cXML is a minor gap.