Skip to main content
Glama
cmendezs

mcp-einvoicing-be

validate_invoice_be

Validates UBL 2.1 XML invoices against Belgian EN 16931 rules and Peppol BIS, PINT-BE, or Mercurius profiles. Returns detailed error and warning messages.

Instructions

Validate a UBL 2.1 XML invoice against Belgian business rules.

Applies EN 16931 syntax and semantic checks plus the selected Belgian profile overlay (Peppol BIS Billing 3.0, PINT-BE, or Mercurius). Returns a structured result with per-rule error and warning messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xmlYesRaw UBL 2.1 XML invoice content
profileNoValidation profile: 'peppol-bis-3' (default), 'pint-be', or 'mercurius'peppol-bis-3

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main tool handler function 'validate_invoice_be' — an async method on BEDocumentValidator that validates a UBL 2.1 XML invoice against the selected Belgian profile (peppol-bis-3, pint-be, or mercurius). Calls _validate_with_profile which evaluates XPath-based business rules and returns a structured result dict.
    async def validate_invoice_be(
        self,
        xml: Annotated[str, "Raw UBL 2.1 XML invoice content"],
        profile: Annotated[
            ProfileLiteral,
            "Validation profile: 'peppol-bis-3' (default), 'pint-be', or 'mercurius'",
        ] = "peppol-bis-3",
    ) -> dict[str, object]:
        """Validate a UBL 2.1 XML invoice against Belgian business rules.
    
        Applies EN 16931 syntax and semantic checks plus the selected Belgian
        profile overlay (Peppol BIS Billing 3.0, PINT-BE, or Mercurius).
        Returns a structured result with per-rule error and warning messages.
        """
        try:
            result = self._validate_with_profile(xml, profile)
            return cast(dict[str, object], result.to_dict())
        except ValidationError as exc:
            return {"valid": False, "profile": profile, "errors": [str(exc)], "warnings": []}
  • ProfileLiteral type and _PROFILE_RULES mapping: defines the three allowed profiles ('peppol-bis-3', 'pint-be', 'mercurius') and maps them to their respective rule sets imported from the standards modules.
    ProfileLiteral = Literal["peppol-bis-3", "pint-be", "mercurius"]
    
    _PROFILE_RULES: dict[str, list[dict[str, str]]] = {
        "peppol-bis-3": PEPPOL_BIS3_RULES,
        "pint-be": PINT_BE_RULES,
        "mercurius": MERCURIUS_RULES,
    }
  • Tool registration: BEDocumentValidator is instantiated and validate_invoice_be is registered via mcp.tool()(_validator.validate_invoice_be) on the FastMCP instance in _register_be_tools.
    def _register_be_tools(mcp: Any) -> None:
        """Register all Belgian e-invoicing tools onto the shared FastMCP instance."""
        mcp.tool()(_validator.validate_invoice_be)
        mcp.tool()(_validator.validate_pint_be)
        mcp.tool()(_generator.generate_invoice_be)
        mcp.tool()(transform_to_ubl)
        mcp.tool()(lookup_vat_be)
        mcp.tool()(check_peppol_participant_be)
        mcp.tool()(get_invoice_types_be)
    
    
    mcp = EInvoicingMCPServer(
        "mcp-einvoicing-be",
        instructions=(
            "Tools for Belgian electronic invoicing: validation, generation, and lookups "
            "for Peppol BIS Billing 3.0, PINT-BE (NBB), UBL 2.1, and Mercurius."
        ),
    )
    mcp.register_plugin(_register_be_tools, "be")
  • Helper function 'parse_ubl_xml' used by the validator to parse raw XML string into an ElementTree. Returns (root, None) on success or (None, error_str) on ParseError.
    def parse_ubl_xml(xml: str) -> tuple[Element | None, str | None]:
        """Parse a UBL XML string and return ``(root_element, None)`` or ``(None, error_str)``."""
        try:
            return fromstring(xml.strip()), None
        except ParseError as exc:
            return None, f"XML parse error: {exc}"
  • PEPPOL_BIS3_RULES definition — the base business rules (BR-01, BR-02) used by the default 'peppol-bis-3' profile and extended by PINT-BE and Mercurius.
    PEPPOL_BIS3_RULES: list[dict[str, str]] = [
        {
            "id": "BR-01",
            "severity": "error",
            "xpath": "/Invoice/cbc:CustomizationID",
            "message": "An Invoice shall have a Specification identifier (BT-24).",
        },
        {
            "id": "BR-02",
            "severity": "error",
            "xpath": "/Invoice/cbc:ProfileID",
Behavior4/5

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

Describes applying syntax and semantic checks and returning structured results. Without annotations, the description adequately covers behavior, though no mention of permissions or side effects.

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?

Two concise sentences that front-load purpose and action, with no redundant information.

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?

With output schema present and complete parameter descriptions, the description provides sufficient context for an agent to use the tool 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 coverage is 100%, baseline 3. Description adds value by explaining profiles (Peppol BIS, PINT-BE, Mercurius) and default, enhancing understanding beyond schema.

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?

Explicitly states it validates a UBL 2.1 XML invoice against Belgian business rules, listing specific profiles. Clearly distinguishes from sibling tools like validate_pint_be.

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?

Indicates when to use (for Belgian validation) but does not explicitly exclude scenarios or point to alternatives beyond the sibling list.

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/cmendezs/mcp-einvoicing-be'

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