Skip to main content
Glama
cmendezs

mcp-einvoicing-be

get_invoice_types_be

Retrieve supported Belgian e-invoice document types including invoice, credit note, and debit note with their UBL customizationID and profileID values for Peppol BIS Billing 3.0 and PINT-BE profiles.

Instructions

Return the supported Belgian e-invoice document types.

Includes invoice (380), credit note (381), and debit note (383) with their UBL customizationID and profileID values for each supported profile (Peppol BIS Billing 3.0 and PINT-BE).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler/execution function for the 'get_invoice_types_be' tool. Returns the supported Belgian e-invoice document types (380, 381, 383) with their Peppol BIS Billing 3.0 and PINT-BE profile information, sourced from the INVOICE_TYPES constant.
    async def get_invoice_types_be() -> dict[str, object]:
        """Return the supported Belgian e-invoice document types.
    
        Includes invoice (380), credit note (381), and debit note (383) with their
        UBL ``customizationID`` and ``profileID`` values for each supported profile
        (Peppol BIS Billing 3.0 and PINT-BE).
        """
        return {"invoice_types": INVOICE_TYPES}
  • INVOICE_TYPES constant defining the supported document types (380 Invoice, 381 Credit note, 383 Debit note) with multilingual names and associated profiles (peppol-bis-3 and pint-be), each having customization_id and profile_id values. This is the data returned by the handler.
    # Supported Belgian e-invoice document types
    INVOICE_TYPES: list[dict[str, object]] = [
        {
            "code": "380",
            "name": "Invoice",
            "name_fr": "Facture",
            "name_nl": "Factuur",
            "profiles": {
                "peppol-bis-3": {
                    "customization_id": CUSTOMIZATION_IDS["peppol-bis-3"],
                    "profile_id": PROFILE_IDS["peppol-bis-3"],
                },
                "pint-be": {
                    "customization_id": CUSTOMIZATION_IDS["pint-be"],
                    "profile_id": PROFILE_IDS["pint-be"],
                },
            },
        },
        {
            "code": "381",
            "name": "Credit note",
            "name_fr": "Note de crédit",
            "name_nl": "Creditnota",
            "profiles": {
                "peppol-bis-3": {
                    "customization_id": CUSTOMIZATION_IDS["peppol-bis-3"],
                    "profile_id": PROFILE_IDS["peppol-bis-3"],
                },
                "pint-be": {
                    "customization_id": CUSTOMIZATION_IDS["pint-be"],
                    "profile_id": PROFILE_IDS["pint-be"],
                },
            },
        },
        {
            "code": "383",
            "name": "Debit note",
            "name_fr": "Note de débit",
            "name_nl": "Debietnota",
            "profiles": {
                "peppol-bis-3": {
                    "customization_id": CUSTOMIZATION_IDS["peppol-bis-3"],
                    "profile_id": PROFILE_IDS["peppol-bis-3"],
                },
            },
        },
    ]
  • Registration of 'get_invoice_types_be' as an MCP tool via mcp.tool() decorator, making it available as a callable tool on the MCP server.
    mcp.tool()(get_invoice_types_be)
  • Import of get_invoice_types_be from the lookup module into the server entry point for registration.
    from mcp_einvoicing_be.tools.lookup import (
        check_peppol_participant_be,
        get_invoice_types_be,
        lookup_vat_be,
    )
  • CUSTOMIZATION_IDS and PROFILE_IDS constants used as building blocks for the INVOICE_TYPES data structure. These define the UBL customizationID (BT-24) and profileID (BT-23) values for each profile.
    CUSTOMIZATION_IDS: dict[str, str] = {
        "peppol-bis-3": ("urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0"),
        "pint-be": (
            "urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0"
            "#conformant#urn:fdc:www.nbb.be:2020:pintbe"
        ),
    }
    
    # UBL profileID values (BT-23)
    PROFILE_IDS: dict[str, str] = {
        "peppol-bis-3": "urn:fdc:peppol.eu:2017:poacc:billing:01:1.0",
        "pint-be": "urn:fdc:peppol.eu:2017:poacc:billing:01:1.0",
    }
Behavior4/5

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

No annotations provided, but description clearly states the tool returns data (document types with specific identifiers). No side effects or auth needs required for a simple read operation. Could mention response format but sufficient.

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 sentences, front-loaded with purpose, no wasted words. Each sentence adds specific details about return content.

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?

Given no parameters and an output schema exists, description fully covers the tool's functionality. Provides enough context for an AI agent to understand what it returns and when to use it.

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

Parameters5/5

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

Tool has no parameters; description adds value by explaining what the output contains (invoice types with UBL customizationID and profileID). Baseline 4 for 0 parameters, raised to 5 for adding output semantics.

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?

Description explicitly states the tool returns supported Belgian e-invoice document types, listing specific types (invoice, credit note, debit note) and includes UBL customizationID and profileID values. Clearly distinguishes from sibling tools that handle validation, generation, or lookup.

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?

Implied usage as a reference tool for supported document types, but no explicit guidance on when to use this versus siblings like check_peppol_participant_be or lookup_vat_be. No exclusions or when-not-to-use mentioned.

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