EDI 834 MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EDI_834_DIR | Yes | The one folder the server is allowed to read 834 files from. Paths outside it are refused. Files, including carrier profile JSON files, must be inside this directory. |
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 |
|---|---|
| validate_834A | Validate a HIPAA X12 005010X220A1 (834) benefit enrollment file before it goes to a carrier. Checks the envelope (ISA/GS/ST counts and control numbers), header (BGN, sponsor, payer), every member (relationship, maintenance codes, subscriber ID, SSN structure, birth date, age limits) and every coverage (insurance line, coverage tier, begin/end dates, retro and future dates, terminations without end dates, employee-only tiers with dependents enrolled). Each finding has a rule ID, severity, segment position, plain-English message and fix. Names, SSNs and birth dates are never included unless show_pii=true. Pass a carrier profile (inline or profile_path) to apply companion-guide rules. Set platform="workday_ccb_834_v2" for files from Workday Cloud Connect for Benefits 834 V2: each finding then says where in Workday to fix it (map, attribute, service, security or data). |
| summarize_834A | Summarize an 834 file without PII: sender/receiver, file date, full vs change file, sponsor and payer, member/subscriber/dependent counts, actions (adds, changes, terminations) and coverage lines and tiers. |
| compare_834A | Compare two 834 files for the same group (e.g. last week's and this week's) and report what changed: members added or missing, coverages added, terminated or missing, tier and plan changes, begin-date and demographic changes. When the new file is a full file (BGN08 RX or 4), members or coverages missing from it are flagged as potential unintended terminations — the most common cause of coverage gaps. |
| explain_834_codeB | Explain an 834 code, or list a whole code table. Tables: relationship, maintenance_type, maintenance_reason, benefit_status, employment_status, insurance_line, coverage_level, date_qualifier, bgn_purpose, bgn_action, gender, id_qualifier. |
| workday_834_setup_guideA | Step-by-step setup of Workday's "Cloud Connect for Benefits: ANSI X12 834 V2" connector: ISU and security group, creating the integration system, choosing the transmission service, integration attributes, maps, field attributes, population eligibility and overrides, delivery, and the test loop with validate_834 and compare_834. Each section lists common pitfalls. |
| choose_workday_834_serviceB | Pick the right CCB ANSI X12 834 V2 transmission service from what the carrier requires (change file or full file, and how terminations must be reported). Exactly one service may be enabled. |
| get_default_profileB | Show the baseline validation settings that a carrier profile can override. |
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 7 tools
Each tool has a clearly distinct purpose: validation, summarization, comparison, code explanation, setup guidance, service selection, and baseline profile inspection. The Workday-related tools are complementary rather than overlapping, so an agent can select the right one without confusion.
Most names follow a readable snake_case verb_noun pattern, often with the 834 domain marker. The main deviation is workday_834_setup_guide, which is noun-led rather than verb-led, but overall the naming remains predictable and clear.
Seven tools is well-scoped for an EDI 834 validation and Workday setup assistant. Each tool covers a meaningful workflow step without redundant or filler operations.
The surface covers core validation, inspection, comparison, code lookup, and Workday setup guidance well. A minor gap is profile management: agents can inspect default settings and pass profiles, but there is no tool to create, list, or edit carrier profiles.