Skip to main content
Glama

Avanciq - tax rates, codes, e-invoices, calculation checks

Validate an e-invoice (EN 16931)

einvoice_check
Read-onlyIdempotent

2 calls. Runs the official CEN EN 16931 business rules (validation artefacts, unmodified) on a UBL 2.1 Invoice/CreditNote or UN/CEFACT CII (also the XML inside Factur-X/ZUGFeRD). Returns VALID/INVALID, each failed rule id with where it fails and how to fix it. Use it whenever asked if an e-invoice is valid or why it was rejected - reading XML by eye misses arithmetic and code-list rules. XML is checked in memory, not stored.

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": {
      "xml": "<xml>"
    },
    "name": "einvoice_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlYesThe complete invoice XML document as text.
rulesetNoOptional; auto detects UBL vs CII.auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description still adds real behavioral context: rules are the unmodified official artefacts, XML is processed in memory and not stored, and it costs '2 calls'. It does not discuss size limits, failure modes for malformed XML, or error behavior, which keeps it at a 3.

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?

Four tight sentences, front-loaded with scope and accepted formats before usage guidance and the return shape. The opening '2 calls' is terse but informative and nothing is padded.

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?

With no output schema, the description carries the burden of describing returns and does so (VALID/INVALID plus each failed rule id with failure location and fix). Gaps remain around malformed-input handling and the exact response structure, but an agent has enough to call it correctly.

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 coverage is 100%, so both parameters are already documented including the ruleset enum and auto-detection. The description contributes one piece of extra meaning, that the xml parameter may be the XML embedded inside Factur-X/ZUGFeRD, but adds nothing about size limits or format handling beyond that, so the 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?

The description names a specific verb and resource ('Runs the official CEN EN 16931 business rules') plus the exact accepted formats (UBL 2.1 Invoice/CreditNote, UN/CEFACT CII, embedded Factur-X/ZUGFeRD XML), which clearly separates it from a sibling like einvoice_rule that presumably explains a single rule.

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?

It gives an explicit trigger ('Use it whenever asked if an e-invoice is valid or why it was rejected') and justifies itself against manual inspection ('reading XML by eye misses arithmetic and code-list rules'). It does not name an alternative tool or state when not to use it, so it stops short of a 5.

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