Skip to main content
Glama
Sign In
mcp-edi

mcp-edi

by MaestroMed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Parse ANSI X12

parse_x12

Parse raw ANSI X12 interchange into structured JSON. Deduces delimiters from the ISA segment and returns hierarchy with transaction type recognition and verification.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "parse_x12"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesRaw X12 interchange starting with ISA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description bears full burden. It discloses delimiter deduction logic (element separator, component separator, segment terminator), return structure (ISA/GS/ST hierarchy, decomposed segments), transaction type recognition, and counter/control-number verification. It does not mention error handling or size limits, but coverage is good.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: first states the main purpose, second provides key behavioral details. No fluff. Every sentence adds value.

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

Completeness5/5

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

The tool is moderately complex (parses structured EDI), has no output schema, and one parameter. The description covers return hierarchy, segment decomposition, transaction type recognition, and verification. This is complete for the tool's purpose.

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

Parameters3/5

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

Schema coverage is 100% with one required parameter 'message' described as 'Raw X12 interchange starting with ISA'. The description adds no additional parameter-level semantics beyond the schema, so baseline 3 is appropriate.

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?

The description uses specific verbs ('Parse', 'deduced', 'Returns') and names the resource ('raw ANSI X12 interchange', 'structured JSON'). It distinguishes from siblings like parse_edifact and parse_cxml by explicitly stating it handles X12 format and mentions specific transaction types (850, 856, 810, 997...).

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?

The description clearly indicates the tool is for parsing X12 interchanges, and siblings handle other formats (EDIFACT, cXML) or other operations (validate, explain, generate). It does not explicitly state when not to use it, but the context is clear.

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

Deploy Server

Other Tools