mcp-facturacion-electronica-es

by cmendezs

Overview Schema Source Related Servers Discussions Admin

Remote

Es Parse Aeat Response

es__parse_aeat_response

Parse AEAT XML responses into structured JSON to extract submission status, verification code, and error details.

Instructions

Analiza y normaliza una respuesta XML de la AEAT (VERI*FACTU o SII) a JSON estructurado.

Extrae EstadoEnvio, CSV (código seguro de verificación) y detalle de errores.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`xml`	Yes	Respuesta XML de la AEAT en crudo.
`response_type`	No	Tipo de respuesta a analizar (por defecto: 'verifactu').	verifactu

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.8.0Aug 26, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedInput schema / properties / response_type / enum
```
Removed value: -[
-  "verifactu",
-  "sii"
-]
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedv0.0.1May 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are present, so the description carries the burden of behavioral disclosure. It does explain that XML is normalized into JSON and that EstadoEnvio, CSV, and error details are extracted, but it does not describe behavior on malformed XML, encoding assumptions, or the lack of side effects.

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?

The definition is compact and front-loaded: the action appears in the first sentence, and the extracted fields in the second. There is no filler, though the 'VERI*FACTU' typo and lack of formatting keep it from being perfect.

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 two-parameter tool with 100% schema coverage and an output schema, the description provides the essential purpose and the key extracted fields, so an agent can invoke it correctly. It lacks explicit usage conditions, but that gap is captured by the usage-guidelines dimension.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by implying that response_type selects between VERI*FACTU and SII, which complements the schema's bare default of 'verifactu'. The xml parameter is mostly restated by the schema.

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 uses a specific verb ('Analiza y normaliza'), identifies the exact resource ('respuesta XML de la AEAT (VERI*FACTU o SII)') and the output ('JSON estructurado'). It also names the extracted fields, which clearly distinguishes it from the sibling generation, submission, and status tools.

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 intended use is only implied: an agent would infer to call this tool after receiving an AEAT XML response. It does not explicitly state when to prefer this over siblings, list prerequisites, or mention cases where this tool should not be used.

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