mcp-facturacion-electronica-es

Overview Schema Source Related Servers Discussions Admin

Es Validate Facturae Schema

es__validate_facturae_schema

Validates Facturae XML against the official 3.2.2 XSD, performing structural and schema checks to ensure compliance with Spanish electronic invoicing standards.

Instructions

Valida un XML Facturae contra el XSD oficial 3.2.2.

Realiza validación estructural y, si el XSD está disponible en resources/facturae/, también validación de esquema completa.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`xml`	Yes	XML Facturae a validar.
`schema_version`	No	Versión del esquema (por defecto: '3.2.2').	3.2.2

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.8.0Aug 26, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedv0.0.1May 14, 2026

TDQS

A3.8/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 usefully discloses the conditional behavior that complete schema validation only happens if the XSD is available, but it does not state whether the operation is read-only, how errors are returned, or what happens if schema_version differs from 3.2.2.

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?

The description is two short sentences with no filler. The core purpose is front-loaded, and the second sentence adds the key conditional behavior without redundancy.

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 simple two-parameter validator with an output schema, the description covers purpose and the main behavioral condition clearly. It is slightly incomplete in not explicitly guiding the agent among the many related e-invoicing siblings, but it is adequate for low-complexity invocation.

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 input schema already documents both parameters. The description adds no additional parameter-level semantics beyond restating the default XSD version, so the baseline score of 3 is appropriate.

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 states a specific verb ('Valida'), an exact resource ('XML Facturae'), and a precise standard ('XSD oficial 3.2.2'). This clearly distinguishes the tool from generation, signing, submission, and other Spanish e-invoicing siblings.

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 purpose implies use for validating Facturae XML against a schema, but it does not explicitly explain when to choose this over related validation tools or mention exclusions. The only conditional guidance is about XSD availability, which is more behavioral than usage-oriented.

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