SignalEDI MCP Server

Official

by SignalEDI

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Generate Test Document

generate_test_document

Read-onlyIdempotent

Generate synthetic X12 test documents (850, 810, 856, 837) with optional overrides for date, PO number, and control number. Provides honest capability labels and rejects unsupported formats.

Instructions

Render a synthetic X12 sample for the local inventory (850/810/856 baseline, 837 Professional partial). Returns an honest capability label. controlNumber and the transaction's primary date apply to every fixture; poNumber applies only to 850 and 810. Refuses EDIFACT, HL7, and unknown sets. Local only; works in the docs profile. Local read-only operation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	Yes	Local fixture codes: 850, 810, 856, 837. 837 means Professional 005010X222A1 only.
`overrides`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tool`	No
`type`	No
`error`	No
`content`	No
`message`	No
`requestId`	No
`capability`	No
`validationErrors`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv0.4.1Sep 17, 2026

addedInput schema / properties / overrides / properties / controlNumber / maxLength
```
Added value: +9
```
addedInput schema / properties / overrides / properties / controlNumber / minLength
```
Added value: +9
```
addedInput schema / properties / overrides / properties / controlNumber / pattern
```
Added value: +"^\\d{9}$"
```

changedInput schema / properties / overrides / properties / date / description

Previous value: -"YYYYMMDD"New value: +"YYYYMMDD primary transaction date: PO date (850), invoice date (810), shipment date (856), or claim creation/service date (837 Professional)."

addedInput schema / properties / overrides / properties / date / pattern
```
Added value: +"^\\d{8}$"
```
addedInput schema / properties / overrides / properties / poNumber / description
```
Added value: +"Purchase-order reference for 850 and 810 only."
```
addedInput schema / properties / overrides / properties / poNumber / maxLength
```
Added value: +40
```
addedInput schema / properties / overrides / properties / poNumber / minLength
```
Added value: +1
```

changedInput schema / properties / type / description

Previous value: -"Transaction set to generate."New value: +"Local fixture codes: 850, 810, 856, 837. 837 means Professional 005010X222A1 only."

removedInput schema / properties / type / enum

Removed value: -[
-  "850",
-  "810",
-  "856",
-  "837"
-]

addedInput schema / properties / type / maxLength
```
Added value: +16
```
addedInput schema / properties / type / minLength
```
Added value: +2
```

addedInput schema / properties / type / pattern

Added value: +"^[A-Za-z0-9][A-Za-z0-9/_-]{0,15}$"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "type",
+        "capability",
+        "content"
+      ]
+    },
+    {
+      "required": [
+        "error",
+        "message"
+      ]
+    }
+  ],
+  "properties": {
+    "capability": {
+      "enum": [
+        "baseline",
+        "partial"
+      ],
+      "type": "string"
+    },
+    "content": {
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "requestId": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "type": {
+      "enum": [
+        "850",
+        "810",
+        "856",
+        "837"
+      ],
+      "type": "string"
+    },
+    "validationErrors": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.4.0Aug 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description reinforces 'Local read-only operation.' It adds valuable behavioral context beyond annotations: refusal behavior for non-supported standards, the 'honest capability label' return, and parameter applicability rules. No contradiction with annotations.

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?

The description is compact (three sentences) and front-loaded with the core purpose. Each sentence earns its place: purpose, capability label, parameter scoping, and operational constraints. No redundancy or filler.

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 simple (2 params, 1 required, nested overrides) and the description covers the essential behavior: what it generates, which types are supported, how parameters apply, what it refuses, and that it is local and read-only. The presence of an output schema covers return structure, so the description is complete for an agent to select and call it correctly.

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

Parameters4/5

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

Schema description coverage is 50%, and the description compensates by explaining that controlNumber and primary date apply to every fixture, while poNumber applies only to 850 and 810. This adds meaning beyond the raw schema, which only gives per-parameter descriptions for type and date. The description also clarifies the 837 meaning as Professional 005010X222A1.

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 clearly states the tool renders synthetic X12 samples for specific transaction types (850/810/856 baseline, 837 Professional partial), with a specific verb ('render') and resource ('synthetic X12 sample'). It also names the capability label return, distinguishing it from sibling tools like search_docs or lookup_x12, which serve different purposes.

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 provides clear usage context: it is local-only, works in the docs profile, and explicitly refuses EDIFACT, HL7, and unknown sets. It also clarifies which parameters apply to which fixture types. While it doesn't explicitly contrast with alternatives, the tool's unique role as the only generator among siblings makes the usage context clear.

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

Deploy Server