Skip to main content
Glama
jmcaamanog

CE3X-MCP-Server

by jmcaamanog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Proponer Medidas Mejora Rd390

proponer_medidas_mejora_rd390
Read-onlyIdempotent

Generate the three RD 390/2021 improvement measure packages for existing building energy certificates, with emission cuts, annual bill savings, and payback periods.

Instructions

Genera automáticamente los 3 paquetes de medidas de mejora exigidos por el Real Decreto 390/2021 (Mejora de Envolvente SATE, Sustitución por Aerotermia y Solución Integral con Solar FV), calculando reducción de emisiones, ahorro en factura (€/año) y periodo de amortización (payback).

Cuándo usar: Invoque esta herramienta preceptivamente en todo certificado energético de edificio existente para cumplimentar el Anexo III de Medidas de Mejora. Para auditar subvenciones NextGen use 'emitir_dictamen_subvenciones_nextgen'.

Comportamiento y efectos secundarios: Operación de cálculo analítico y financiero (Read-Only). No modifica archivos en disco. Emite progreso interactivo a FastMCP.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tipo_acsNoSistema de ACS actual del edificio.EfectoJoule
zona_climaticaNoZona climática CTE DB-HE asignada.C1
superficie_utilYesSuperficie útil del inmueble en m².
ano_construccionYesAño de construcción catastral del edificio.
tipo_calefaccionNoSistema de calefacción actual del edificio.EfectoJoule

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / ano_construccion / description
      Added value: +"Año de construcción catastral del edificio."
    • addedInput schema / properties / ano_construccion / maximum
      Added value: +2050
    • addedInput schema / properties / ano_construccion / minimum
      Added value: +1800
    • addedInput schema / properties / superficie_util / description
      Added value: +"Superficie útil del inmueble en m²."
    • addedInput schema / properties / superficie_util / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / tipo_acs / description
      Added value: +"Sistema de ACS actual del edificio."
    • addedInput schema / properties / tipo_calefaccion / description
      Added value: +"Sistema de calefacción actual del edificio."
    • addedInput schema / properties / zona_climatica / description
      Added value: +"Zona climática CTE DB-HE asignada."
  2. First observedv1.5.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered structurally. The description adds useful context beyond that: it specifies analytical/financial computation, that no files on disk are modified, and that interactive progress is emitted to FastMCP. The 'Read-Only' phrasing partly restates the annotation, capping it below 5.

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?

Front-loaded purpose followed by clearly labeled sections ('Cuándo usar', 'Comportamiento y efectos secundarios'). Efficient overall, with only minor redundancy where 'Read-Only' overlaps the readOnlyHint annotation.

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?

With an output schema present, return values need not be explained, and the description correctly focuses on purpose, usage and side effects. It is complete enough for correct invocation, though it could specify the relationship to the downstream Anexo III workflow more concretely.

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 schema already documents all five parameters (superficie_util, ano_construccion, tipo_acs, zona_climatica, tipo_calefaccion) with defaults and ranges. The description mentions the computed outputs but adds no per-parameter meaning beyond the schema, matching the baseline 3.

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 names a specific verb and resource ('Genera automáticamente los 3 paquetes de medidas de mejora') and enumerates exactly what those packages are (SATE, Aerotermia, Solar FV). It also differentiates from the sibling tool 'emitir_dictamen_subvenciones_nextgen', so an agent can route correctly without opening the schema.

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

Usage Guidelines5/5

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

The 'Cuándo usar' section explicitly instructs preceptive invocation for every existing-building energy certificate to complete Anexo III, and names the alternative tool for the NextGen subsidy audit case. Both the when-to-use and the disambiguating alternative are stated.

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

Deploy Server

Other Tools