Skip to main content
Glama
cmendezs

mcp-facturacion-electronica-es

es__submit_to_face

Submits a XAdES-signed Facturae XML to the FACe B2B API, using the required unit, office, and body codes. Automates electronic invoice submission for Spanish public administration.

Instructions

Envía un XML Facturae firmado con XAdES a FACe (Punto General de Entrada de Facturas Electrónicas) a través de la API REST B2B de FACe v2. Requiere FACE_ENV, FACE_CLIENT_ID y FACE_CLIENT_SECRET.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xmlYesXML Facturae con firma XAdES.
administrative_unitYesCódigo UnidadTramitadora de FACe.
accounting_officeYesCódigo OficinasContables de FACe.
management_bodyYesCódigo OrganoGestor de FACe.

Implementation Reference

  • Handler function `handle_es_submit_to_face` — sends a signed Facturae XML to FACe via REST API v2. Extracts params (xml, administrative_unit, accounting_office, management_body), authenticates with OAuth2 client credentials, POSTs the XML with metadata to the FACe /facturas endpoint, and returns the response.
    async def handle_es_submit_to_face(
        arguments: dict[str, Any],
    ) -> list[types.TextContent]:
        try:
            from mcp_einvoicing_core.http_client import AuthMode, BaseEInvoicingClient, OAuthConfig
    
            xml_str = arguments.get("xml", "")
            admin_unit = arguments.get("administrative_unit", "")
            accounting_office = arguments.get("accounting_office", "")
            management_body = arguments.get("management_body", "")
    
            for name, val in [
                ("xml", xml_str), ("administrative_unit", admin_unit),
                ("accounting_office", accounting_office), ("management_body", management_body),
            ]:
                if not val:
                    return err(f"{name} is required", "MISSING_PARAM")
    
            client_id = os.environ.get("FACE_CLIENT_ID", "")
            client_secret = os.environ.get("FACE_CLIENT_SECRET", "")
            if not client_id or not client_secret:
                return err(
                    "FACE_CLIENT_ID y FACE_CLIENT_SECRET son obligatorios.",
                    "MISSING_CONFIG",
                )
    
            env = face_env()
            base_url = FACE_BASE_URLS[env]
    
            # [NEED: verify FACe OAuth2 token endpoint URL for sandbox and production]
            oauth_cfg = OAuthConfig(
                token_url=f"{base_url}/oauth/token",
                client_id=client_id,
                client_secret=client_secret,
            )
            client = BaseEInvoicingClient(
                base_url=base_url,
                auth_mode=AuthMode.OAUTH2_CLIENT_CREDENTIALS,
                oauth_config=oauth_cfg,
            )
    
            xml_bytes = xml_str.encode() if isinstance(xml_str, str) else xml_str
            payload = {
                "unidadTramitadora": admin_unit,
                "oficinasContables": accounting_office,
                "organoGestor": management_body,
            }
            response = await client._request(
                "POST",
                "/facturas",
                json=payload,
                files={"factura": ("factura.xml", xml_bytes, "application/xml")},
            )
    
            return ok({
                "status_code": response.status_code,
                "environment": env,
                "response": response.json() if response.headers.get("content-type", "").startswith("application/json") else response.text[:2000],
            })
    
        except Exception as exc:
            logger.exception("es__submit_to_face failed")
            return err(str(exc))
  • Tool definition `TOOL_ES_SUBMIT_TO_FACE` — defines the name 'es__submit_to_face', description, and inputSchema requiring xml (string), administrative_unit, accounting_office, and management_body (all strings).
    TOOL_ES_SUBMIT_TO_FACE = types.Tool(
        name="es__submit_to_face",
        description=(
            "Envía un XML Facturae firmado con XAdES a FACe (Punto General de Entrada de Facturas "
            "Electrónicas) a través de la API REST B2B de FACe v2. "
            "Requiere FACE_ENV, FACE_CLIENT_ID y FACE_CLIENT_SECRET."
        ),
        inputSchema={
            "type": "object",
            "properties": {
                "xml": {"type": "string", "description": "XML Facturae con firma XAdES."},
                "administrative_unit": {
                    "type": "string",
                    "description": "Código UnidadTramitadora de FACe.",
                },
                "accounting_office": {
                    "type": "string",
                    "description": "Código OficinasContables de FACe.",
                },
                "management_body": {
                    "type": "string",
                    "description": "Código OrganoGestor de FACe.",
                },
            },
            "required": ["xml", "administrative_unit", "accounting_office", "management_body"],
        },
    )
  • Registration in `_TOOL_HANDLERS` dict mapping the string 'es__submit_to_face' to `handle_es_submit_to_face`, plus inclusion of `TOOL_ES_SUBMIT_TO_FACE` in the `_ALL_TOOLS` list at line 87.
    _TOOL_HANDLERS: dict[str, Any] = {
        # VERI*FACTU
        "es__generate_verifactu_record":      handle_es_generate_verifactu_record,
        "es__validate_verifactu_record":      handle_es_validate_verifactu_record,
        "es__submit_verifactu_to_aeat":       handle_es_submit_verifactu_to_aeat,
        "es__generate_qr_verifactu":          handle_es_generate_qr_verifactu,
        "es__cancel_verifactu_record":        handle_es_cancel_verifactu_record,
        # Facturae / FACe
        "es__generate_facturae_xml":          handle_es_generate_facturae_xml,
        "es__sign_facturae_xades":            handle_es_sign_facturae_xades,
        "es__submit_to_face":                 handle_es_submit_to_face,
        "es__get_face_invoice_status":        handle_es_get_face_invoice_status,
        "es__validate_facturae_schema":       handle_es_validate_facturae_schema,
        # SII
        "es__build_sii_invoice_record":       handle_es_build_sii_invoice_record,
        "es__submit_sii_batch":               handle_es_submit_sii_batch,
        "es__query_sii_status":               handle_es_query_sii_status,
        "es__generate_sii_correction":        handle_es_generate_sii_correction,
        # TicketBAI
        "es__generate_ticketbai_xml":         handle_es_generate_ticketbai_xml,
        "es__submit_ticketbai":               handle_es_submit_ticketbai,
        "es__validate_ticketbai_schema":      handle_es_validate_ticketbai_schema,
        # Crea y Crece / B2B
        "es__generate_b2b_einvoice_es":       handle_es_generate_b2b_einvoice_es,
        "es__check_b2b_mandate_applicability": handle_es_check_b2b_mandate_applicability,
        # Utilities
        "es__detect_regional_regime":         handle_es_detect_regional_regime,
        "es__get_compliance_status":          handle_es_get_compliance_status,
        "es__parse_aeat_response":            handle_es_parse_aeat_response,
    }
  • Helper constant `FACE_BASE_URLS` providing sandbox and production base URLs for the FACe B2B REST API v2, used by the handler.
    #: FACe B2B REST API v2 base URLs
    FACE_BASE_URLS: dict[str, str] = {
        "sandbox": "https://se-face.redsara.es/factura-face-b2b-api/api/v2",
        "production": "https://face.gob.es/factura-face-b2b-api/api/v2",
        # [NEED: verify — FACe may have changed API base path in 2025]
    }
  • Helper function `face_env()` — reads the FACE_ENV environment variable (defaulting to 'sandbox') to select the target FACe environment.
    def face_env() -> str:
        """Return 'sandbox' or 'production' from FACE_ENV (default: 'sandbox')."""
        raw = os.environ.get("FACE_ENV", "sandbox").lower().strip()
        if raw not in {"sandbox", "production"}:
            logger.warning("Unknown FACE_ENV value %r — defaulting to 'sandbox'", raw)
            return "sandbox"
        return raw
Behavior2/5

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

No annotations are present, so the description must cover behavioral traits. It only mentions authentication requirements; it does not disclose success/failure behavior, side effects, or idempotency. This is insufficient for a submission tool.

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 sentences with no unnecessary words. The first sentence clearly states the action, and the second lists requirements. It is well-structured and front-loaded.

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

Completeness2/5

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

Given no output schema or annotations, the description should explain return values or processing outcomes. It does not mention what the agent can expect (e.g., a tracking ID). Missing contextual information about the FACe system or Spanish e-invoicing context.

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% with clear descriptions for each parameter. The tool description adds no additional meaning beyond what is already in the schema. Baseline 3 is appropriate.

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 submits a signed XML Facturae to FACe via the specific API v2. It distinguishes from siblings like es__get_face_invoice_status and es__sign_facturae_xades, which handle different steps.

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 mentions prerequisites (environment variables) but does not provide guidance on when to use this tool versus alternatives or when not to use it. It implies the tool is for submission after signing, but lacks explicit context.

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-facturacion-electronica-es'

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