CE3X-MCP-Server

Overview Schema Source Related Servers Discussions Admin

Calcular Sombras Hueco

calcular_sombras_hueco

Read-onlyIdempotent

Calculate summer and winter shading reduction factors and modified solar factor Fs for glazed openings with overhangs, recesses, or eaves per CTE DB-HE.

Instructions

Calcula los factores reductores de sombra estacionales (verano e invierno) y el factor solar modificado Fs para huecos acristalados debidos a elementos de sombra propios (voladizos, retranqueos y aleros) según CTE DB-HE.

Cuándo usar: Utilice esta herramienta para calcular la protección solar propia de las ventanas del edificio. Para obstáculos remotos frente al edificio (edificios de enfrente, árboles lejanos), use 'calcular_sombras_obstaculo_edificio_enfrente'.

Comportamiento y efectos secundarios: Operación analítica de solo lectura (Read-Only). No modifica archivos ni registros locales.

Input Schema

TableJSON Schema

Name	Required	Description
`orientacion`	Yes	Orientación del hueco: 'Sur', 'Norte', 'Este', 'Oeste', 'Sureste', 'Suroeste', 'Noreste', 'Noroeste'.
`tiene_toldo`	No	Indica si el hueco dispone de toldo u obstáculo móvil exterior de protección solar.
`alto_hueco_m`	Yes	Alto de la ventana en metros (m).
`retranqueo_m`	No	Profundidad del retranqueo de la ventana respecto al plano exterior de fachada en metros (m).
`ancho_hueco_m`	Yes	Ancho de la ventana en metros (m).
`vuelo_voladizo_m`	No	Saliente o vuelo del voladizo o alero superior en metros (m).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 17, 2026
- removedInput schema / properties / alto_hueco_m / default
```
Removed value: -1.2
```
- addedInput schema / properties / alto_hueco_m / description
```
Added value: +"Alto de la ventana en metros (m)."
```
- addedInput schema / properties / alto_hueco_m / exclusiveMinimum
```
Added value: +0
```
- removedInput schema / properties / ancho_hueco_m / default
```
Removed value: -1.2
```
- addedInput schema / properties / ancho_hueco_m / description
```
Added value: +"Ancho de la ventana en metros (m)."
```
- addedInput schema / properties / ancho_hueco_m / exclusiveMinimum
```
Added value: +0
```
- removedInput schema / properties / orientacion / default
```
Removed value: -"Sur"
```
- addedInput schema / properties / orientacion / description
```
Added value: +"Orientación del hueco: 'Sur', 'Norte', 'Este', 'Oeste', 'Sureste', 'Suroeste', 'Noreste', 'Noroeste'."
```
- addedInput schema / properties / retranqueo_m / description
```
Added value: +"Profundidad del retranqueo de la ventana respecto al plano exterior de fachada en metros (m)."
```
- addedInput schema / properties / retranqueo_m / minimum
```
Added value: +0
```
- addedInput schema / properties / tiene_toldo / description
```
Added value: +"Indica si el hueco dispone de toldo u obstáculo móvil exterior de protección solar."
```
- addedInput schema / properties / vuelo_voladizo_m / description
```
Added value: +"Saliente o vuelo del voladizo o alero superior en metros (m)."
```
- addedInput schema / properties / vuelo_voladizo_m / minimum
```
Added value: +0
```
- addedInput schema / required
```
Added value: +[
+  "orientacion",
+  "ancho_hueco_m",
+  "alto_hueco_m"
+]
```
First observedv1.5.1Oct 17, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the read-only nature is covered structurally. The 'Comportamiento' section largely restates this ('operación de solo lectura, no modifica archivos'), adding only the minor detail that no local records are affected. No additional behavioral traits (idempotency, determinism, rate limits) are disclosed beyond the annotations.

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 front-loaded with the core computation and organized into labeled sections ('Cuándo usar', 'Comportamiento'), so each block is easy to scan. There is mild redundancy in restating read-only status already in the annotations, keeping it just short of optimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return values, and annotations carry the safety profile. The purpose, scope, standard, and sibling routing are all covered, so an agent has everything needed to invoke the tool correctly.

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 tying the domain concepts (voladizos, retranqueos, aleros) directly to the shading computation, which maps the agent to the vuelo_voladizo_m, retranqueo_m and related parameters, giving slightly more than the schema alone.

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) and precise resource: factores reductores de sombra estacionales (verano/invierno) and factor solar modificado Fs para huecos acristalados. It names the exact scope (elementos de sombra propios: voladizos, retranqueos, aleros) and the governing standard (CTE DB-HE), making it easy to distinguish from the sibling tool.

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?

A dedicated 'Cuándo usar' section tells the agent exactly when to use this tool (protección solar propia de las ventanas) and names the explicit alternative for the contrasting case ('calcular_sombras_obstaculo_edificio_enfrente' for remote obstacles). Both the when and when-not conditions 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