facturolia-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FACTUROLIA_LANG | No | Response language, 'en' or 'fr'. Defaults to 'en'. | en |
| FACTUROLIA_API_KEY | Yes | Your Facturolia API key (required). | |
| FACTUROLIA_BASE_URL | No | Override the base URL for testing. Defaults to 'https://facturolia.fr'. | https://facturolia.fr |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_invoiceA | Extract the full contents of one electronic invoice file (Factur-X, ZUGFeRD, XRechnung, UBL or CII) as plain text: invoice number and dates, supplier and customer, every line, the VAT breakdown per rate, totals, IBAN, the EN 16931 consistency check, and whether the amounts on a Factur-X PDF's visible page match its embedded XML. Use it when the user wants to know what an invoice contains. If they only ask whether the invoice is correct, use check_invoice instead, which returns the verdict without the contents. Side effects: the file is uploaded over HTTPS to the Facturolia API, processed in memory and discarded; nothing is written locally. Requires FACTUROLIA_API_KEY; files over 10 MB are refused; requests are rate limited per key tier and a 429 error means wait and retry. |
| check_invoiceA | Validate one electronic invoice file (Factur-X, ZUGFeRD, XRechnung, UBL or CII) against the EN 16931 standard and return only the verdict and the list of anomalies: totals that do not add up, VAT miscalculated for a rate, missing required fields, each with the rule code and the figures involved. Use it to answer 'is this invoice correct?' or to screen several files quickly. It does not list the invoice contents; for parties, lines and totals use read_invoice. This is a consistency check, not a legal compliance certificate, and it does not transmit the invoice to any tax platform. Side effects: the file is uploaded over HTTPS to the Facturolia API, processed in memory and discarded. Requires FACTUROLIA_API_KEY; 10 MB limit; rate limited per key tier. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: read_invoice extracts full contents while check_invoice returns only the validation verdict. Their descriptions explicitly cross-reference each other to prevent confusion, so an agent can easily select the right one.
Both tool names follow a consistent verb_noun pattern (read_invoice, check_invoice), using snake_case and clear action words. The only minor deviation is that they are not from the same action family (read vs. check), but this is acceptable given the distinct operations.
With only 2 tools, the surface is quite thin, but for a focused invoice-processing server that offers exactly two complementary operations (read and check), it may be sufficient. However, typical MCP servers have more tools, so this feels slightly minimal.
The domain appears to be electronic invoice handling, and the two tools cover content extraction and validation. Missing operations include invoice creation, listing, or deletion, but for an analysis/validation service, these might be out of scope. Still, there is no way to manage invoices, so the surface is incomplete for a full lifecycle.