Tailprint

generate_einvoice

Generate legally compliant European e-invoices (Factur-X/ZUGFeRD/EN 16931) as visual PDFs with embedded XML, ready for ERP and accounting platform ingestion.

Instructions

Generates a legally compliant European hybrid electronic invoice (Factur-X / ZUGFeRD 2.2 / EN 16931). Renders a beautiful visual PDF and embeds machine-readable CrossIndustryInvoice XML (/EmbeddedFiles) for automated ingestion by ERP and accounting platforms (DATEV, SAP, Chorus Pro, Dinero, Billy).

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_number": "<invoice_number>",
      "seller_name": "<seller_name>",
      "buyer_name": "<buyer_name>",
      "line_items": "<line_items>"
    },
    "name": "generate_einvoice"
  }
}

Input Schema

Name	Required	Description	Default
`notes`	No	Optional payment terms or notes
`profile`	No	Factur-X compliance profile level	BASIC
`currency`	No	ISO 4217 currency code (e.g. EUR, DKK, USD, SEK)	EUR
`due_date`	No	Due payment date (YYYY-MM-DD)
`buyer_city`	No	Buyer city
`buyer_name`	Yes	Customer/buyer company or client name
`line_items`	Yes	List of invoice items or billed services
`buyer_email`	No	Buyer contact/AP email
`payment_bic`	No	Bank SWIFT/BIC code
`seller_city`	No	Seller city
`seller_name`	Yes	Supplier/seller company name
`buyer_street`	No	Buyer street address
`buyer_vat_id`	No	Buyer VAT ID / Tax number (e.g. "DE123456789")
`payment_iban`	No	Bank transfer IBAN for direct wire payment
`seller_email`	No	Seller billing email
`buyer_country`	No	2-letter ISO country code of buyer (e.g. DE, FR, DK)	DE
`seller_street`	No	Seller street address
`seller_vat_id`	No	Supplier VAT ID / Tax number (e.g. "DK12345678" or "DE987654321")
`buyer_postcode`	No	Buyer postal code
`invoice_number`	Yes	Unique invoice reference number (e.g. "INV-2026-0042")
`seller_country`	No	2-letter ISO country code of seller (e.g. DK, DE, FR, NL)	DK
`seller_postcode`	No	Seller postal code

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Nov 13, 2026

TDQS

A3.7/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 behavioral burden. It usefully discloses the hybrid PDF/XML output and compliance standards, but it does not explain how the generated file is returned, whether it is persisted, or what validation/error behavior to expect.

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, front-loaded with the core purpose and then the output/ingestion behavior. "Beautiful" is minor marketing language but does not undermine the otherwise efficient structure.

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?

For a 22-parameter generation tool with no annotations and no output schema, the description covers purpose and output format but omits return mechanics, persistence, and error/validation behavior. It is adequate but leaves meaningful gaps for an agent invoking it.

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 description coverage is 100%, so the schema already documents all 22 parameters. The description adds no parameter-level meaning beyond naming standards and target platforms, so the baseline of 3 applies.

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 uses a specific verb, "Generates," and a precise resource, "European hybrid electronic invoice," naming Factur-X / ZUGFeRD 2.2 / EN 16931. It clearly distinguishes this from generic PDF siblings by describing a legally compliant hybrid invoice output.

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 implies usage for legally compliant European e-invoices and names ERP/accounting ingestion platforms, but it does not explicitly state when to choose this over render_pdf or other PDF tools, nor does it provide exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server