Skip to main content
Glama

universal_peppol_bis3_validator

Read-onlyIdempotent

[Universal CEN/EN 16931 & Peppol BIS Billing 3.0 validator. Deterministic calculation, read-only, side-effect free]. Audits structured e-invoices against CEN/EN 16931 semantic standards and OpenPeppol UBL 2.1 Schematron rules, calculating tax subtotals, line extension totals, and payable amounts with decimal.js precision. Usage: Use this tool to validate cross-border e-invoices before dispatching to Peppol Access Points or European buyers. Returns: JSON object with { invoiceNumber: string, isCenEn16931Compliant: boolean, isPeppolBis3Compliant: boolean, validationStatus: string, financialTotals: object, vatSubtotals: array, violationsFound: array }.

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": {
      "invoiceNumber": "<invoiceNumber>",
      "issueDateIso": "<issueDateIso>",
      "senderVatId": "<senderVatId>",
      "senderEndpointId": "<senderEndpointId>",
      "receiverVatId": "<receiverVatId>",
      "receiverEndpointId": "<receiverEndpointId>",
      "buyerReferenceOrOrderNumber": "<buyerReferenceOrOrderNumber>",
      "invoiceLines": "<invoiceLines>"
    },
    "name": "universal_peppol_bis3_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueDateIsoNoPayment due date in YYYY-MM-DD format
senderVatIdYesSeller statutory VAT number with country prefix (e.g. IT01234567890)
currencyCodeNoInvoice currency (default: EUR)
invoiceLinesYesArray of invoice item lines
issueDateIsoYesInvoice issue date in YYYY-MM-DD format
invoiceNumberYesUnique invoice identifier (cbc:ID)
receiverVatIdYesBuyer statutory VAT number with country prefix
senderEndpointIdYesSeller Peppol Electronic Address Scheme (EAS) identifier (e.g. 0201:IT01234567890)
receiverEndpointIdYesBuyer Peppol EAS endpoint identifier (e.g. 0201:IT98765432100)
allowanceChargeAmountEurNoOptional surcharge or document-level discount in EUR
buyerReferenceOrOrderNumberYesBuyer reference or purchase order number (cbc:BuyerReference)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds real context beyond them: deterministic execution, side-effect freedom, decimal.js precision for arithmetic, and precisely which totals it computes. The explicit return field list compensates for the absence of an output schema. It repeats 'read-only, side-effect free' from the annotations, which is wasted, and says nothing about how violations are ranked or whether validation aborts on first error.

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

Conciseness4/5

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

Structurally front-loaded with a bracketed standard/safety tagline, then Usage, then Returns — an agent can scan it quickly. Minor waste in restating read-only and side-effect-free, which the annotations already carry.

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 an 11-parameter, read-only validator with no output schema, the description covers purpose, trigger, computation scope, and the response shape in three compact blocks. What is missing is guidance on interpreting results — e.g. whether isCenEn16931Compliant=false with an empty violationsFound array is possible, or how blocking versus warning violations are distinguished.

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 per-parameter documentation is already handled by the schema, and the description adds no field-level semantics. A baseline 3 is appropriate; nothing in the prose clarifies edge cases like the allowanceChargeAmountEur sign convention or the currency default behavior.

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?

Names a specific action (audit/validate) and resource (structured e-invoices) plus the exact standards enforced: CEN/EN 16931 semantic rules and OpenPeppol UBL 2.1 Schematron. The scope (tax subtotals, line extension totals, payable amounts) separates it from sibling validators like ted_eforms_notice_validator or dpp_payload_validator without needing to open the schema.

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 'Usage' line gives a concrete trigger: validate cross-border e-invoices before dispatching to Peppol Access Points or European buyers. It does not state when NOT to use it or name an alternative tool for domestic/non-Peppol invoices, so it stops short of full routing guidance.

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