CE3X-MCP-Server

Overview Schema Source Related Servers Discussions Admin

Emitir Dictamen Subvenciones Nextgen

emitir_dictamen_subvenciones_nextgen

Read-onlyIdempotent

Generate the technical compliance report and official opinion for Next Generation EU subsidies and IRPF deductions, verifying the 30% non-renewable primary energy reduction.

Instructions

Genera el informe técnico justificativo y dictamen oficial de cumplimiento para las subvenciones Next Generation EU (RD 853/2021) y deducciones fiscales en IRPF (40%/60%).

Cuándo usar: Utilice esta herramienta para justificar el cumplimiento del requisito normativo de reducción del 30% en consumo de energía primaria no renovable para tramitar ayudas públicas.

Comportamiento y efectos secundarios: Operación analítica de evaluación económica y normativa (Read-Only). No altera archivos.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tipo_acs`	No	Sistema de ACS actual.	EfectoJoule
`paquete_mejora`	No	Paquete de mejora a evaluar: 1 (Envolvente SATE), 2 (Aerotermia) o 3 (Integral con Solar FV).
`zona_climatica`	No	Zona climática CTE DB-HE.	C1
`superficie_util`	Yes	Superficie útil habitable en m².
`ano_construccion`	Yes	Año de construcción del inmueble.
`tipo_calefaccion`	No	Sistema de calefacción actual.	EfectoJoule

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 17, 2026
- addedInput schema / properties / ano_construccion / description
```
Added value: +"Año de construcción del inmueble."
```
- addedInput schema / properties / ano_construccion / maximum
```
Added value: +2050
```
- addedInput schema / properties / ano_construccion / minimum
```
Added value: +1800
```
- addedInput schema / properties / paquete_mejora / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  }
+]
```
- addedInput schema / properties / paquete_mejora / description
```
Added value: +"Paquete de mejora a evaluar: 1 (Envolvente SATE), 2 (Aerotermia) o 3 (Integral con Solar FV)."
```
- removedInput schema / properties / paquete_mejora / type
```
Removed value: -"integer"
```
- addedInput schema / properties / superficie_util / description
```
Added value: +"Superficie útil habitable en m²."
```
- addedInput schema / properties / superficie_util / exclusiveMinimum
```
Added value: +0
```
- addedInput schema / properties / tipo_acs / description
```
Added value: +"Sistema de ACS actual."
```
- addedInput schema / properties / tipo_calefaccion / description
```
Added value: +"Sistema de calefacción actual."
```
- addedInput schema / properties / zona_climatica / description
```
Added value: +"Zona climática CTE DB-HE."
```
First observedv1.5.1Oct 17, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this ('operación analítica... Read-Only. No altera archivos') and adds that it performs economic and normative evaluation producing a report. It does not contradict annotations and adds mild context, but repeats the read-only fact the annotation already carries.

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?

Front-loaded purpose followed by clearly labeled 'Cuándo usar' and 'Comportamiento y efectos secundarios' sections. Every sentence earns its place with no redundancy or filler.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The description covers purpose and usage adequately; only sibling differentiation and richer behavioral detail are missing, which are minor given the structured data available.

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 all six parameters (tipo_acs, paquete_mejora, zona_climatica, superficie_util, ano_construccion, tipo_calefaccion) are documented in the schema itself. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Genera) and concrete deliverables (informe técnico justificativo y dictamen oficial de cumplimiento) plus the regulatory scope (RD 853/2021, IRPF 40%/60%). This is far more specific than a tautology, though it does not explicitly contrast itself with similar siblings such as generar_certificado_completo.

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

Usage Guidelines4/5

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

The 'Cuándo usar' section gives an explicit trigger: justifying compliance with the 30% non-renewable primary energy reduction requirement to process public aid. However it names no alternatives or when-not conditions, so the agent gets context but no routing guidance against sibling tools.

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

Deploy Server