mcp-facturacion-electronica-es

Overview Schema Source Related Servers Discussions Admin

Es Validate Verifactu Record

es__validate_verifactu_record

Validates a VERI*FACTU XML record, ensuring structural correctness and schema compliance when the official XSD is available.

Instructions

Valida un registro VERI*FACTU XML.

Realiza validación estructural y, si el XSD v1.0 (HAC/1177/2024) está disponible en resources/verifactu/, también validación de esquema.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`xml`	Yes	Registro VERI*FACTU XML en crudo.
`schema_version`	No	Versión del esquema XSD (por defecto: '1.0').	1.0

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

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly discloses that structural validation is always performed and schema validation only when the XSD is available at a specific path. This conditional behavior is valuable and goes beyond the basic purpose, though it does not mention side effects (likely none) or error semantics.

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 concise and front-loads the main purpose in the first sentence, then adds a relevant detail about conditional schema validation. No unnecessary words or repetition.

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?

Given that the tool has an output schema (not shown but noted) and the description explains the validation logic including the XSD availability condition, the description is largely complete. It could mention how schema_version influences XSD selection, but this is a minor gap and likely covered by the parameter description.

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% for both parameters (xml and schema_version), so the schema already documents them. The description adds no additional parameter information, so the baseline of 3 applies.

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 clearly states the tool validates a VERI*FACTU XML record and distinguishes it from siblings like generation, submission, and query tools. The verb 'valida' plus the resource 'registro VERI*FACTU XML' makes the purpose specific and unambiguous.

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 description implies the tool is for validating VERI*FACTU XML records, but it does not explicitly state when to use it versus alternatives (e.g., validate_facturae_schema for Facturae). It mentions the conditional schema validation but lacks explicit usage scenarios or exclusions.

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