Agent Decision & Evidence Tools (MCP + x402)

E-invoice validation

validate_einvoice_eu

Read-onlyIdempotent

Validate an XRechnung, ZUGFeRD/Factur-X or Peppol BIS invoice (UBL or CII) against EN 16931: mandatory fields, arithmetic consistency of all totals, VAT breakdown and category rules, each finding with its official BR- rule code.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`xml`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	No
`error`	No
`valid`	No
`errors`	No
`source`	No
`syntax`	No
`charged`	No	When present on an error, false means the failed result is uncharged.
`message`	No
`missing`	No
`profile`	No
`receipt`	No
`settled`	No	When present on an error, false means no settlement occurred.
`summary`	No
`unknown`	No
`accepted`	No
`standard`	No
`warnings`	No
`retryable`	No
`checked_at`	No
`disclaimer`	No
`error_code`	No
`extensions`	No
`schematron`	No
`error_count`	No
`status_code`	No
`did_you_mean`	No
`document_type`	No
`warning_count`	No
`missing_checks`	No
`full_schematron`	No
`customization_id`	No
`partial_evidence`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 6, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / xml / minLength
```
Added value: +1
```
removedInput schema / properties / xml / title
```
Removed value: -"Xml"
```

removedInput schema / title

Removed value: -"validate_einvoice_toolArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "valid",
+        "syntax",
+        "source",
+        "profile",
+        "customization_id",
+        "document_type",
+        "summary",
+        "error_count",
+        "errors",
+        "warning_count",
+        "warnings",
+        "full_schematron",
+        "schematron",
+        "checked_at",
+        "standard",
+        "disclaimer",
+        "receipt",
+        "extensions"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "description": "Structured result contract for validate_einvoice_eu. A success satisfies the documented success branch. A domain or tool error includes error and is not a successful settlement; unpaid x402 requirements are carried by the transport wrapper.",
+  "properties": {
+    "accepted": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "charged": {
+      "description": "When present on an error, false means the failed result is uncharged.",
+      "type": "boolean"
+    },
+    "checked_at": {
+      "type": "string"
+    },
+    "customization_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "did_you_mean": {
+      "additionalProperties": true,
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "document_type": {
+      "type": "string"
+    },
+    "error": {
+      "oneOf": [
+        {
+          "type": "string"
+        },
+        {
+          "additionalProperties": true,
+          "properties": {
+            "code": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "message": {
+              "type": "string"
+            },
+            "param": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "message"
+          ],
+          "type": "object"
+        }
+      ]
+    },
+    "error_code": {
+      "type": "string"
+    },
+    "error_count": {
+      "type": "integer"
+    },
+    "errors": {
+      "items": {},
+      "type": "array"
+    },
+    "extensions": {
+      "additionalProperties": true,
+      "properties": {
+        "delivery-receipt": {
+          "additionalProperties": true,
+          "properties": {
+            "how_to_verify": {
+              "type": "string"
+            },
+            "issued_at": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "issuer": {
+              "type": "string"
+            },
+            "issuer_key": {
+              "type": "string"
+            },
+            "key_id": {
+              "type": "string"
+            },
+            "result_hash": {
+              "type": "string"
+            },
+            "service": {
+              "type": "string"
+            },
+            "signature": {
+              "type": "string"
+            },
+            "signed_message": {
+              "type": "string"
+            },
+            "standard": {
+              "const": "eucompliance-receipt/2",
+              "type": "string"
+            },
+            "subject": {
+              "type": "string"
+            },
+            "valid_until": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "verify_url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "standard",
+            "service",
+            "subject",
+            "result_hash",
+            "issued_at",
+            "valid_until",
+            "issuer",
+            "issuer_key",
+            "key_id",
+            "verify_url",
+            "how_to_verify",
+            "signature",
+            "signed_message"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "delivery-receipt"
+      ],
+      "type": "object"
+    },
+    "full_schematron": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "missing": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "missing_checks": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "partial_evidence": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "profile": {
+      "type": "string"
+    },
+    "receipt": {
+      "additionalProperties": true,
+      "properties": {
+        "how_to_verify": {
+          "type": "string"
+        },
+        "issued_at": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "issuer": {
+          "type": "string"
+        },
+        "issuer_key": {
+          "type": "string"
+        },
+        "key_id": {
+          "type": "string"
+        },
+        "result_hash": {
+          "type": "string"
+        },
+        "service": {
+          "type": "string"
+        },
+        "signature": {
+          "type": "string"
+        },
+        "signed_message": {
+          "type": "string"
+        },
+        "standard": {
+          "const": "eucompliance-receipt/2",
+          "type": "string"
+        },
+        "subject": {
+          "type": "string"
+        },
+        "valid_until": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "verify_url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "standard",
+        "service",
+        "subject",
+        "result_hash",
+        "issued_at",
+        "valid_until",
+        "issuer",
+        "issuer_key",
+        "key_id",
+        "verify_url",
+        "how_to_verify",
+        "signature",
+        "signed_message"
+      ],
+      "type": "object"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "schematron": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "settled": {
+      "description": "When present on an error, false means no settlement occurred.",
+      "type": "boolean"
+    },
+    "source": {
+      "type": "string"
+    },
+    "standard": {
+      "type": "string"
+    },
+    "status_code": {
+      "type": "integer"
+    },
+    "summary": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "syntax": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "unknown": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "valid": {
+      "type": "boolean"
+    },
+    "warning_count": {
+      "type": "integer"
+    },
+    "warnings": {
+      "items": {},
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedJul 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive behavior. The description adds the scope of validation (mandatory fields, totals arithmetic, VAT breakdown/category rules) and states that results include official BR- rule codes, which is useful behavioral context beyond the annotations. No contradiction.

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?

One dense, front-loaded sentence with no filler. It names the resource, formats, validation standard, checks performed, and output format in a compact structure.

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 single-input validation tool with an output schema and read-only annotations, the description is nearly complete. The only notable gap is explicit parameter input guidance; everything else an agent needs to call it is present.

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%, and the description never explicitly defines the xml parameter. The acceptable invoice format list makes it inferable that xml should contain the invoice XML, but the description does not state whether raw XML, a path, or an encoding is expected, leaving the agent to infer from the parameter name.

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 opens with a specific verb and resource: 'Validate an XRechnung, ZUGFeRD/Factur-X or Peppol BIS invoice (UBL or CII) against EN 16931'. It lists concrete validation categories and mentions BR- rule codes, so it is clearly distinguishable from sibling validation tools such as validate_vat or check_counterparty_eu.

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?

The domain is clearly stated: use it for European e-invoice XML validation against EN 16931. It does not explicitly name alternatives or exclusion conditions, but the format list and BR-rule output make the intended use unambiguous.

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

All Agent Decision & Evidence Tools (MCP + x402) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.