mcp-facturacion-electronica-es

by cmendezs

Overview Schema Source Related Servers Discussions Admin

Remote

Es Generate Sii Correction

es__generate_sii_correction

Create SII correction records (A1 modification or A4 cancellation) by referencing the original invoice ID.

Instructions

Genera un registro de modificación SII (A1) o baja (A4).

Referencia la factura original mediante IDFactura.

Input Schema

TableJSON Schema

Name	Required	Description
`record_type`	Yes	'issued' o 'received'.
`correction_type`	Yes	'A1' (modificación) o 'A4' (baja).
`original_invoice`	Yes	Factura original que se rectifica.
`corrected_invoice`	No	Datos corregidos. Omitir para una baja (A4).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.8.0Aug 26, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / corrected_invoice / anyOf
```
Added value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / corrected_invoice / default
```
Added value: +null
```
- changedInput schema / properties / corrected_invoice / description
```
Previous value: -"Datos corregidos. Omitir o null para una baja (A4)."New value: +"Datos corregidos. Omitir para una baja (A4)."
```
- removedInput schema / properties / corrected_invoice / type
```
Removed value: -"object"
```
- addedInput schema / properties / correction_type / description
```
Added value: +"'A1' (modificación) o 'A4' (baja)."
```
- removedInput schema / properties / correction_type / enum
```
Removed value: -[
-  "A1",
-  "A4"
-]
```
- addedInput schema / properties / original_invoice / additionalProperties
```
Added value: +true
```
- addedInput schema / properties / record_type / description
```
Added value: +"'issued' o 'received'."
```
- removedInput schema / properties / record_type / enum
```
Removed value: -[
-  "issued",
-  "received"
-]
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedv0.0.1May 14, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states only that it generates a record and references the original invoice via IDFactura; it does not indicate side effects, whether the record is submitted, or if validation occurs. This is minimal for a statutory tax tool.

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 two-sentence description is entirely focused: first sentence states the action, the second adds the key referencing detail. No filler, irrelevant info, or redundant restatement of the tool name.

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 the output schema exists and the input schema has 100% coverage with useful descriptions, the description adds the essential missing detail (IDFactura reference). However, it does not clarify the relationship with the submission workflow or the expected format of the returned correction record, which would slightly improve completeness.

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%, but the description adds meaningful semantics not present in the schema: 'Referencia la factura original mediante IDFactura' tells the agent that original_invoice must be identified by IDFactura. This is genuine extra information about the original_invoice parameter.

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 generates an SII correction record (A1 modification) or cancellation (A4), which is a specific verb and resource. It also references the original invoice via IDFactura, distinguishing it from sibling tools that generate Verifactu or build regular SII invoice records.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance is given on when to use this tool versus alternatives. The description does not mention any exclusions, prerequisites, or references to sibling tools like es__build_sii_invoice_record or es__submit_sii_batch. The only usage hint is the schema note about omitting corrected_invoice for A4, which is not in the description.

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