Skip to main content
Glama

AICTIONBOT™ Werkbank

E-invoice checker: reads an XRechnung or ZUGFeRD XML (UBL or CII) and checks mandatory details and arithmetic

check_einvoice
Read-onlyIdempotent

AICTIONBOT™ e-invoice checker by KULIC Advisory (tool 49). Takes the XML of an e-invoice in UBL or UN/CEFACT CII syntax (XRechnung, ZUGFeRD or Factur-X) and reads number, dates, seller, buyer, VAT IDs, purchase order reference, lines, totals, tax per rate and payment details. Checks the mandatory details (red if missing, yellow for purchase order reference, delivery date and IBAN), whether net plus tax equals gross, whether the lines add up to the net total, tax per rate and the amount due, and flags profiles that are not valid as an e-invoice (MINIMUM, BASIC WL). Checks mandatory details and arithmetic, not a full validation against the schema and rules of the standard. Not tax advice. Deterministic, no AI, nothing stored. Needs sign-in: runs with an AICTIONBOT™ Werkbank licence; without a licence one check per connection every 30 days is free (sign in with “Connect without a licence”).

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": "check_einvoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlYesThe XML of the e-invoice (UBL or CII). For ZUGFeRD PDFs the embedded XML file.
languageNoLanguage of the answer. Default de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond that: it discloses the licensing requirement, the free tier rate limit (one check per connection every 30 days), the sign-in path, that the operation is deterministic with no AI, and that nothing is stored. Authentication and quota behavior are exactly the kind of facts annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence, but the leading 'AICTIONBOT™ e-invoice checker by KULIC Advisory (tool 49)' is pure branding and internal numbering that costs attention without helping selection. The long run-on second sentence mixes the field inventory, the check list, and the red/yellow flag semantics.

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 two-parameter checker with no output schema, this covers what an agent needs: input formats, the specific checks performed, the red/yellow severity convention, invalid profiles (MINIMUM, BASIC WL), and the auth/quota situation. The only shortfall is that the shape of the response is implied rather than described, which matters somewhat since no output schema exists.

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 xml and language parameters are already documented in the schema, including the ZUGFeRD embedded-XML case. The description restates the accepted syntaxes but adds no new meaning for either parameter and never mentions the language option; baseline 3 applies when the schema does the heavy lifting.

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: takes e-invoice XML in UBL or CII (XRechnung, ZUGFeRD, Factur-X) and checks mandatory fields plus arithmetic. The scope is concrete and the field list (number, dates, VAT IDs, lines, totals, tax per rate) makes the capability unambiguous. It does not explicitly distinguish itself from the sibling check_invoice, which is the only thing keeping it from a 5.

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?

It carves out the boundary of the tool ('Checks mandatory details and arithmetic, not a full validation against the schema and rules of the standard' and 'Not tax advice'), which is useful when-not guidance. However, it never says when to prefer this over the similarly named check_invoice or check_invoice_payment, so the routing decision is left to the agent.

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.