Skip to main content
Glama
Hochfrequenz

TransformerBee.MCP

by Hochfrequenz

convert_bo4e_to_edifact

Convert BO4E transaction data to EDIFACT format for German energy market communication. Specify format version for compatibility.

Instructions

Convert a BO4E transaktion to its EDIFACT equivalent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transaktionYes
edifact_format_versionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function decorated with @mcp.tool, implementing the conversion logic using TransformerBeeClient. Input schema via type hints: BOneyComb transaktion and optional EdifactFormatVersion.
    @mcp.tool(description="Convert a BO4E transaktion to its EDIFACT equivalent")
    async def convert_bo4e_to_edifact(
        ctx: Context,  # type:ignore[type-arg] # no idea what the second type arg is
        transaktion: BOneyComb,
        edifact_format_version: EdifactFormatVersion | None = None,
    ) -> str:
        """Tool that uses initialized resources"""
        if not edifact_format_version:
            edifact_format_version = get_current_edifact_format_version()
        client: TransformerBeeClient = ctx.request_context.lifespan_context.transformerbeeclient
        try:
            edifact = await client.convert_to_edifact(boney_comb=transaktion, edifact_format_version=edifact_format_version)
        except Exception:
            _logger.exception("Error while converting BO4E to edifact")
            raise
        await ctx.info(f"Successfully converted BO4E to EDIFACT with format version {edifact_format_version}")
        return edifact
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the conversion action but doesn't describe any behavioral traits such as error handling, performance characteristics, side effects, or output format details. The description is minimal and lacks context about what the conversion entails or any operational constraints.

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 extremely concise with a single sentence that directly states the tool's function. It is front-loaded and wastes no words, making it easy to parse quickly. Every word earns its place by conveying the core purpose without unnecessary elaboration.

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

Completeness3/5

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

Given the tool's complexity (data format conversion with 2 parameters, 0% schema coverage, and no annotations), the description is incomplete. It doesn't explain parameter semantics, behavioral traits, or usage context. However, the presence of an output schema mitigates the need to describe return values, keeping it from being entirely inadequate.

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

Parameters2/5

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

Schema description coverage is 0%, meaning parameters are undocumented in the schema. The description mentions 'BO4E transaction' and 'EDIFACT equivalent' but doesn't explain the parameters 'transaktion' or 'edifact_format_version', their formats, or how they influence the conversion. It adds minimal semantic value beyond what's implied by the tool name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: converting a BO4E transaction to EDIFACT format. It specifies the verb 'convert' and the resources involved (BO4E transaction to EDIFACT equivalent), making the function unambiguous. However, it doesn't explicitly differentiate from its sibling tool 'convert_edifact_to_bo4e' beyond 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling tool 'convert_edifact_to_bo4e' or any other conversion methods, nor does it specify prerequisites, contexts, or exclusions for usage. The agent must infer usage based solely on the tool name and description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hochfrequenz/TransformerBee.mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server