Skip to main content
Glama

NovaPixel LexGrid

einvoice_xml_auditor

Audit FatturaPA 1.2.2 and Peppol BIS 3.0 XML against official XSD and business rules (SDI error codes, decimal recalculation, Bollo > 77.47€), or build compliant XML from simplified JSON.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "einvoice_xml_auditor"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo'audit' to validate XML or 'builder' to generate XMLaudit
itemsNoItems array with unitPrice, quantity, vatRate, natura (in builder mode)
senderNoSender object (in builder mode)
paymentNoOptional payment details with IBAN and BIC (in builder mode)
documentNoDocument details (number, date, currency) (in builder mode)
recipientNoRecipient object (in builder mode)
xmlContentNoRaw XML string of the invoice (required in audit mode)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add real behavioral value by enumerating what is checked: SDI error codes, decimal recalculation, and the Bollo threshold of 77.47€. However, it never says whether auditing is read-only, whether the builder produces output only in the response or writes a file, or how findings are reported, which leaves meaningful gaps for a multi-mode tool.

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?

A single front-loaded sentence puts the audit capability and its standards first, then the builder capability, with the rule details in a parenthetical. It is dense but every clause carries information; a short explicit mode-selection sentence would improve it slightly without bloating it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 7 parameters, zero of which are schema-required, and no output schema or annotations; the description therefore should clarify which fields each mode needs (xmlContent for audit; items/document/sender/recipient for builder) and what the response contains. The schema partially covers the per-mode hints, but the description itself leaves the required-input contract and return shape unstated.

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 every parameter already carries its own description, including mode enum values and the 'in builder mode' qualifiers; baseline 3 applies. The description adds only the business-rule context (XSD, SDI codes, Bollo) rather than clarifying field-level semantics such as required combinations per mode.

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 the specific standards audited (FatturaPA 1.2.2, Peppol BIS 3.0), the artifact (XML against XSD and business rules), and the second capability (building compliant XML from simplified JSON). Nothing about it overlaps with the sibling tools (codice fiscale, IBAN, VAT/KYB), so an agent can route to it unambiguously.

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?

The 'or build...' clause plus the mode enum implies the audit-vs-builder split (audit when you already have XML, builder when you have simplified JSON), but the description never states the selection rule explicitly, nor any prerequisites such as supported document types or when a failed audit should be retried after fixing input.

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