Skip to main content
Glama

validate_zugferd

Validate a ZUGFeRD or Factur-X PDF for compliance against electronic invoice standards. Returns validation result with profile, errors, and warnings.

Instructions

Validate a ZUGFeRD/Factur-X PDF for compliance.

Args: pdf_base64: Base64-encoded PDF with embedded ZUGFeRD data.

Returns: JSON validation result (valid, profile, errors, warnings).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pdf_base64Yes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function for the 'validate_zugferd' tool. It is decorated with @mcp.tool(), receives a base64-encoded PDF, decodes it, calls dg.zugferd.validate(), and returns the JSON result.
    @mcp.tool()
    def validate_zugferd(pdf_base64: str) -> str:
        """Validate a ZUGFeRD/Factur-X PDF for compliance.
    
        Args:
            pdf_base64: Base64-encoded PDF with embedded ZUGFeRD data.
    
        Returns:
            JSON validation result (valid, profile, errors, warnings).
        """
        dg = _get_client()
        result = dg.zugferd.validate(base64.b64decode(pdf_base64))
        from docgen._serialization import to_dict
        return json.dumps(to_dict(result))
  • The @mcp.tool() decorator registers 'validate_zugferd' as an MCP tool on the FastMCP instance.
    @mcp.tool()
  • The _get_client() helper lazily initializes the DocGen API client used by the handler.
    def _get_client():
        """Lazy-initialise the DocGen client."""
        global _client
        if _client is None:
            # Import here so the module can be imported without the SDK installed
            # (useful for schema introspection)
            from docgen import DocGen
    
            api_key = os.environ.get("DOCGEN_API_KEY", "")
            if not api_key:
                raise RuntimeError(
                    "DOCGEN_API_KEY environment variable is required. "
                    "Set it to your DocGen API key before starting the server."
                )
            base_url = os.environ.get("DOCGEN_BASE_URL")
            kwargs: dict[str, Any] = {"api_key": api_key}
            if base_url:
                kwargs["base_url"] = base_url
            _client = DocGen(**kwargs)
        return _client
Behavior2/5

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

No annotations are provided, and the description lacks disclosure of behavioral traits such as side effects, authentication requirements, or limitations. It does mention the return structure but not fully.

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 clear purpose sentence followed by structured Args/Returns, ensuring readability and quick comprehension.

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?

While the description covers the basic validation function and output, it lacks details on supported ZUGFeRD profiles or versions, which would enhance completeness given the sibling context.

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?

With 0% schema coverage, the description adds meaning by explaining 'pdf_base64' as a Base64-encoded PDF with embedded ZUGFeRD data, going beyond the schema's title and type.

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 action ('Validate') and the resource ('ZUGFeRD/Factur-X PDF'), effectively distinguishing it from sibling tools like 'detect_xrechnung' and 'validate_xrechnung'.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'validate_xrechnung'), nor any when-not-to-use or prerequisite conditions.

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/dokmatiq/docgen-sdks'

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