CE3X-MCP-Server

Overview Schema Source Related Servers Discussions Admin

Calcular Produccion Fotovoltaica Pvgis

calcular_produccion_fotovoltaica_pvgis

Read-onlyIdempotent

Calculate solar PV energy production (kWh/year and monthly) via PVGIS to assess self-consumption or justify CTE DB-HE5 compliance.

Instructions

Calcula con precisión científica la producción de energía solar fotovoltaica (kWh/año y mensual) conectando con la API oficial PVGIS de la Comisión Europea (JRC) con radiación satelital SARAH-2.

Cuándo usar: Utilice esta herramienta al evaluar la integración de energía solar fotovoltaica para autoconsumo como medida de mejora o justificación CTE DB-HE5.

Comportamiento y efectos secundarios: Operación de consulta telemática a la API de la Comisión Europea con caché persistente SQLite local (TTL de 90 días). Read-Only.

Input Schema

TableJSON Schema

Name	Required	Description
`latitud`	Yes	Latitud geográfica en grados decimales (ej. 43.3623 para A Coruña, 40.4168 para Madrid).
`longitud`	Yes	Longitud geográfica en grados decimales (ej. -8.4115 para A Coruña, -3.7038 para Madrid).
`azimut_grados`	No	Orientación o azimut de los paneles: 0° Sur, 90° Oeste, -90° Este, 180° Norte. Por defecto 0.0° (Sur).
`potencia_pico_kw`	No	Potencia pico de la instalación solar fotovoltaica en kilovatios (kWp). Por defecto 3.0 kWp.
`inclinacion_grados`	No	Inclinación de los módulos solares respecto a la horizontal en grados (0 a 90°). Por defecto 35.0°.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 17, 2026
- addedInput schema / properties / azimut_grados / description
```
Added value: +"Orientación o azimut de los paneles: 0° Sur, 90° Oeste, -90° Este, 180° Norte. Por defecto 0.0° (Sur)."
```
- addedInput schema / properties / azimut_grados / maximum
```
Added value: +180
```
- addedInput schema / properties / azimut_grados / minimum
```
Added value: +-180
```
- addedInput schema / properties / inclinacion_grados / description
```
Added value: +"Inclinación de los módulos solares respecto a la horizontal en grados (0 a 90°). Por defecto 35.0°."
```
- addedInput schema / properties / inclinacion_grados / maximum
```
Added value: +90
```
- addedInput schema / properties / inclinacion_grados / minimum
```
Added value: +0
```
- addedInput schema / properties / latitud / description
```
Added value: +"Latitud geográfica en grados decimales (ej. 43.3623 para A Coruña, 40.4168 para Madrid)."
```
- addedInput schema / properties / latitud / maximum
```
Added value: +90
```
- addedInput schema / properties / latitud / minimum
```
Added value: +-90
```
- addedInput schema / properties / longitud / description
```
Added value: +"Longitud geográfica en grados decimales (ej. -8.4115 para A Coruña, -3.7038 para Madrid)."
```
- addedInput schema / properties / longitud / maximum
```
Added value: +180
```
- addedInput schema / properties / longitud / minimum
```
Added value: +-180
```
- addedInput schema / properties / potencia_pico_kw / description
```
Added value: +"Potencia pico de la instalación solar fotovoltaica en kilovatios (kWp). Por defecto 3.0 kWp."
```
- addedInput schema / properties / potencia_pico_kw / exclusiveMinimum
```
Added value: +0
```
First observedv1.5.1Oct 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds useful context beyond them: it is a telematic query to the European Commission's PVGIS API, uses SARAH-2 satellite radiation, and maintains a local SQLite cache with a 90-day TTL. It does not cover rate limits or failure modes, but the behavioral picture is substantially richer.

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 description is well structured with front-loaded purpose followed by 'Cuándo usar' and 'Comportamiento' sections. It is efficient overall, though 'con precisión científica' is mildly promotional and the final 'Read-Only' repeats an annotation already visible elsewhere.

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 full schema coverage, existing annotations, and an output schema, the description supplies enough context: what is calculated, when to use it, and the external API/caching behavior. It is nearly complete, though it could mention practical limits or error handling for an API-dependent tool.

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 latitude, longitude, azimuth, peak power, and tilt with examples and defaults. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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?

States a specific verb (Calcula), resource (producción de energía solar fotovoltaica), output units (kWh/año y mensual), and method (API PVGIS / SARAH-2). This clearly distinguishes it from sibling tools like calcular_calificacion_energetica or proponer_medidas_mejora_rd390.

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 a clear context: evaluating solar PV integration for self-consumption as an improvement measure or CTE DB-HE5 justification. It does not name alternatives or explicit when-not-to-use cases, so it stops short of a 5.

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

Deploy Server