Skip to main content
Glama

export_efactura_xml

Generate and return the UBL 2.1 XML for an invoice in e-Factura format with all the e-Factura properties stored on the invoice, without the PDF copy a submission may embed. Does NOT submit to ANAF. For an invoice ANAF has already accepted this is a fresh rendering, not the copy ANAF signed (see get_efactura_archive).

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_id": "<invoice_id>"
    },
    "name": "export_efactura_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoice_idYesInvoice ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that no PDF is embedded, that nothing is submitted, and that for accepted invoices this is a fresh rendering rather than ANAF's signed artifact. It omits what happens if the invoice lacks e-Factura properties or lacks authorization, and doesn't say how the XML is returned (inline string vs. file).

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?

Three sentences, front-loaded with the core action, then the two scoping caveats. Every sentence adds a distinct constraint and none repeats the title or name.

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

Completeness4/5

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

For a one-parameter, annotation-free read/render tool with no output schema, the description covers what is produced (UBL 2.1 XML), what is excluded (PDF, ANAF-signed copy, submission), and where to go instead. The main remaining gap is failure/precondition behavior when the invoice has no stored e-Factura properties.

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% for the single invoice_id parameter, so the schema already does the work. The description adds no constraints on the ID (e.g. whether the invoice must already be e-Factura-enabled), so baseline 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?

States a specific verb and resource ('Generate and return the UBL 2.1 XML for an invoice in e-Factura format') and pins the scope with two exclusions: no embedded PDF and no ANAF submission. An agent can distinguish this from get_efactura_archive and submit_invoice_to_efactura from the description alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Does NOT submit to ANAF' and points to get_efactura_archive when the ANAF-signed copy is wanted, which is clear when-to-use/when-not guidance. It never names the submit tool that would be the alternative for filing, so routing for the submission case is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources