TransformerBee.MCP

convert_edifact_to_bo4e

Converts EDIFACT messages to BO4E format for German energy market data exchange. Optionally specify the format version to align with applicable AHB validity periods.

Instructions

Convert an EDIFACT message to its BO4E equivalent

Input Schema

TableJSON Schema

Name	Required	Description	Default
`edifact`	Yes
`edifact_format_version`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`stammdaten`	Yes
`transaktionsdaten`	Yes
`links`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.0.8May 11, 2026

removedInput schema / $defs

Removed value: -{
-  "EdifactFormatVersion": {
-    "description": "One format version refers to the period in which an AHB is valid.",
-    "enum": [
-      "FV2104",
-      "FV2110",
-      "FV2210",
-      "FV2304",
-      "FV2310",
-      "FV2404",
-      "FV2410",
-      "FV2504",
-      "FV2510",
-      "FV2604",
-      "FV2610"
-    ],
-    "title": "EdifactFormatVersion",
-    "type": "string"
-  }
-}

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / edifact / title
```
Removed value: -"Edifact"
```

changedInput schema / properties / edifact_format_version / anyOf

Previous value: -[
-  {
-    "$ref": "#/$defs/EdifactFormatVersion"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "One format version refers to the period in which an AHB is valid.",
+    "enum": [
+      "FV2104",
+      "FV2110",
+      "FV2210",
+      "FV2304",
+      "FV2310",
+      "FV2404",
+      "FV2410",
+      "FV2504",
+      "FV2510",
+      "FV2604",
+      "FV2610"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / title

Removed value: -"convert_edifact_to_bo4eArguments"

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"BOneyComb is a data structure that represents a \"transaction\" in the marktkommunikation.\n1 transaction is 1 \"Geschäftsvorfall\"."

addedOutput schema / properties

Added value: +{
+  "links": {
+    "anyOf": [
+      {
+        "additionalProperties": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "stammdaten": {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "transaktionsdaten": {
+    "additionalProperties": {
+      "type": "string"
+    },
+    "type": "object"
+  }
+}

addedOutput schema / required

Added value: +[
+  "stammdaten",
+  "transaktionsdaten"
+]

removedOutput schema / title

Removed value: -"convert_edifact_to_bo4eDictOutput"

Changed1 schema field changedv0.0.7May 4, 2026

changedInput schema / $defs / EdifactFormatVersion / enum

Previous value: -[
-  "FV2104",
-  "FV2110",
-  "FV2210",
-  "FV2304",
-  "FV2310",
-  "FV2404",
-  "FV2410",
-  "FV2504",
-  "FV2510",
-  "FV2604"
-]New value: +[
+  "FV2104",
+  "FV2110",
+  "FV2210",
+  "FV2304",
+  "FV2310",
+  "FV2404",
+  "FV2410",
+  "FV2504",
+  "FV2510",
+  "FV2604",
+  "FV2610"
+]

First observedDec 27, 2025

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description alone must disclose behavioral traits. It only says 'convert', omitting any side effects, idempotency, error handling, authentication needs, or other critical behaviors. Minimal transparency.

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

Conciseness4/5

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

The description is a single concise sentence, front-loading the verb and resource. While efficient, it could include more useful context without becoming verbose.

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

Completeness2/5

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

Despite having an output schema, the description fails to explain the conversion process, BO4E context, or how to handle the version parameter. The tool is incomplete for effective agent use.

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

Parameters1/5

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

Schema description coverage is 0%. The description adds no meaning beyond the schema for either parameter. The edifact_format_version parameter has an enum with no explanation of how to choose the version, and edifact has no description at all.

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 action (convert), input (EDIFACT message), and output (BO4E equivalent). It effectively distinguishes from the sibling tool convert_bo4e_to_edifact by specifying the direction of conversion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs. the sibling, no prerequisites, context, or exceptions mentioned. The description only states what it does without any usage conditions.

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

Deploy Server