Skip to main content
Glama

klergrid-eu-einvoice

generate_eu_invoice

Generate a standards-compliant EU e-invoice XML (peppol-ubl, xrechnung-ubl, zugferd-cii, xrechnung-cii, ksef-fa3) from a CanonicalInvoice JSON object. Charges 1 credit.

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": {
      "targetFormat": "<targetFormat>",
      "invoice": "<invoice>"
    },
    "name": "generate_eu_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoiceYes
targetFormatYes
strictValidationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one valuable cost signal ('Charges 1 credit'), but it omits whether generation is deterministic, what happens on validation failure, whether strictValidation changes error behavior or only output, and whether a failed call still consumes a credit.

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?

Two sentences, front-loaded with the action and the concrete format enumeration, then the cost. Nothing is redundant and nothing padding-like; it reads well as a first-line definition.

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?

The tool takes a nested, unconstrained object (invoice) plus an undocumented boolean, has no output schema and no annotations, yet the description does not explain the CanonicalInvoice contract, the effect of strictValidation, or the return shape/error model. For a nested-payload conversion tool this leaves an agent unable to construct a valid call from the definition alone.

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 0%, so the description must compensate and only partly does. It usefully identifies the invoice input as a 'CanonicalInvoice JSON object' (the schema says only type object), and the format list echoes the enum, but it says nothing about the required structure of CanonicalInvoice or what strictValidation actually does.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Generate a standards-compliant EU e-invoice XML') and enumerates the five supported output formats, so the agent knows exactly what comes back. It doesn't explicitly distinguish itself from siblings like generate_sepa_pain001 or parse_eu_document, but the resource is specific enough to be unambiguous.

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?

Usage is implied by the stated input ('from a CanonicalInvoice JSON object') and output formats, so an agent can infer this is the conversion step from a canonical model to a target XML dialect. There is no explicit when-to-use vs. when-not guidance, no prerequisites (e.g., where a CanonicalInvoice comes from, whether parse_eu_document is the inverse), and no exclusion conditions.

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