Skip to main content
Glama
Sign In
mcp-einvoicing-be

mcp-einvoicing-be

by cmendezs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

generate_invoice_be

Generates a valid UBL 2.1 Belgian e-invoice XML from structured data, applying the correct Peppol profile IDs for submission to Peppol or Mercurius.

Instructions

Generate a valid UBL 2.1 Belgian e-invoice XML document from structured data.

Applies the correct customizationID and profileID for the selected Belgian Peppol profile. The output XML is ready for submission to the Peppol network or the Mercurius platform.

Returns a dict with:

  • xml: the generated UBL 2.1 XML string

  • customization_id: the UBL customizationID applied (BT-24)

  • profile_id: the UBL profileID applied (BT-23)

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": {
      "invoice_data": "<invoice_data>"
    },
    "name": "generate_invoice_be"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoTarget profile: 'peppol-bis-3' (default) or 'pint-eu' (EU PINT v1.0.1)peppol-bis-3
invoice_dataYesInvoice fields matching the BEInvoice schema

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.1
    • changedInput schema / properties / profile / description
      Previous value: -"Target profile: 'peppol-bis-3' (default) or 'pint-be'"New value: +"Target profile: 'peppol-bis-3' (default) or 'pint-eu' (EU PINT v1.0.1)"
    • changedInput schema / properties / profile / enum
      Previous value: -[
-  "peppol-bis-3",
-  "pint-be"
-]New value: +[
+  "peppol-bis-3",
+  "pint-eu"
+]
  2. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/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. It discloses the output structure and the fact that it applies customizationID and profileID, but does not mention authentication needs, side effects, or prerequisites.

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 two concise paragraphs with no filler. The first sentence states the purpose, followed by profile handling, then return values. Every sentence adds value.

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

Completeness4/5

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

The description explains what it does, the output format, and the profile application. It could mention error handling or validation of invoice_data, but given the existence of an output schema, it is fairly complete.

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%, so the description adds no additional meaning beyond what the schema already provides. The description does not elaborate on the parameters (e.g., invoice_data structure).

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 generates a UBL 2.1 Belgian e-invoice XML from structured data, specifying the output is ready for Peppol or Mercurius. It distinguishes well from siblings (parsing, validation, checking) by focusing on generation.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives or when not to use it. Usage is implied by the clear purpose, but no explicit guidance is provided.

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