Skip to main content
Glama
Hochfrequenz

TransformerBee.MCP

by Hochfrequenz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TRANSFORMERBEE_HOSTYesThe host URL where transformer.bee is running (e.g., http://localhost:5021)
TRANSFORMERBEE_CLIENT_IDNoOptional client ID for authentication with transformer.bee
TRANSFORMERBEE_CLIENT_SECRETNoOptional client secret for authentication with transformer.bee

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
convert_edifact_to_bo4eC

Convert an EDIFACT message to its BO4E equivalent

convert_bo4e_to_edifactB

Convert a BO4E transaktion to its EDIFACT equivalent

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools serve opposite directions (BO4E to EDIFACT and vice versa), so there is no ambiguity. An agent can select the correct one based on the desired conversion direction.

Naming Consistency5/5

Both tools follow the exact same naming pattern: 'convert_<source>_to_<target>', which is clear and consistent.

Tool Count5/5

Two tools are perfectly appropriate for a focused bidirectional converter. The scope is narrow and complete, with no need for additional tools.

Completeness5/5

The tool set covers the full conversion cycle: both directions are implemented, so there are no gaps for this domain.

Maintenance

ActivityActive
ResponsivenessUnresponsive

Resources