CE3X-MCP-Server

Overview Schema Source Related Servers Discussions Admin

Calcular Sombras Obstaculo Edificio Enfrente

calcular_sombras_obstaculo_edificio_enfrente

Read-onlyIdempotent

Calculate solar elevation angle and shadow profile table for a remote continuous obstacle, such as an opposite building or terrain, to model neighboring shadows per CTE DB-HE Annex E.

Instructions

Calcula el ángulo de elevación solar alfa (grados) y la tabla de perfil de sombras producida por un obstáculo remoto continuo (edificio colindante o frente a fachada) según el Anejo E del CTE DB-HE.

Cuándo usar: Utilice esta herramienta para modelar sombras arrojadas por construcciones vecinas o accidentes topográficos. Para elementos propios del hueco (voladizos, retranqueos, aleros), use 'calcular_sombras_hueco'.

Comportamiento y efectos secundarios: Operación analítica de cálculo geométrico solar (Read-Only). No escribe archivos ni altera estado.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`altura_edificio_m`	Yes	Altura del edificio u obstáculo de enfrente en metros (m) medida por encima del centro del hueco evaluado.
`orientacion_fachada`	Yes	Orientación de la fachada que recibe la sombra: 'Sur', 'Norte', 'Este', 'Oeste', 'Sureste', 'Suroeste', 'Noreste', 'Noroeste'.
`distancia_edificio_m`	Yes	Distancia horizontal en metros (m) desde la fachada del edificio evaluado hasta el obstáculo o edificio de enfrente.
`descripcion_obstaculo`	No	Descripción del obstáculo remoto (ej. 'Edificio de 6 plantas enfrente').	Edificio colindante

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 / altura_edificio_m / description

Added value: +"Altura del edificio u obstáculo de enfrente en metros (m) medida por encima del centro del hueco evaluado."

addedInput schema / properties / altura_edificio_m / exclusiveMinimum
```
Added value: +0
```

removedInput schema / properties / descripcion_obstaculo / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

changedInput schema / properties / descripcion_obstaculo / default
```
Previous value: -nullNew value: +"Edificio colindante"
```

addedInput schema / properties / descripcion_obstaculo / description

Added value: +"Descripción del obstáculo remoto (ej. 'Edificio de 6 plantas enfrente')."

addedInput schema / properties / descripcion_obstaculo / type
```
Added value: +"string"
```

addedInput schema / properties / distancia_edificio_m / description

Added value: +"Distancia horizontal en metros (m) desde la fachada del edificio evaluado hasta el obstáculo o edificio de enfrente."

addedInput schema / properties / distancia_edificio_m / exclusiveMinimum
```
Added value: +0
```
removedInput schema / properties / orientacion_fachada / default
```
Removed value: -"Sur"
```

addedInput schema / properties / orientacion_fachada / description

Added value: +"Orientación de la fachada que recibe la sombra: 'Sur', 'Norte', 'Este', 'Oeste', 'Sureste', 'Suroeste', 'Noreste', 'Noroeste'."

changedInput schema / required

Previous value: -[
-  "distancia_edificio_m",
-  "altura_edificio_m"
-]New value: +[
+  "distancia_edificio_m",
+  "altura_edificio_m",
+  "orientacion_fachada"
+]

First observedv1.5.1Oct 17, 2026

TDQS

A4.3/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, and the description's '(Read-Only). No escribe archivos ni altera estado' largely restates this rather than adding new traits. It does add useful context by naming the governing standard (Anejo E del CTE DB-HE) and the analytical/geometric nature of the operation, but does not disclose anything beyond annotation plus method reference.

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 with the core purpose, then structured into labeled 'Cuándo usar' and 'Comportamiento' blocks. Every sentence is informative and appropriately sized for a 4-parameter analytical tool.

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 needn't explain return values, and it covers purpose, routing to the sibling, and behavioral profile. Combined with full schema coverage and annotations, an agent has everything needed to select and invoke it correctly.

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 four parameters (units, orientation values, defaults). The description adds no parameter-level syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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?

Names a specific verb (calcula) and precise outputs: ángulo de elevación solar alfa y tabla de perfil de sombras de un obstáculo remoto. It explicitly scopes the tool to neighbor buildings/topography and distinguishes itself from the sibling calcular_sombras_hueco.

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?

Contains an explicit 'Cuándo usar' section stating the use case (sombras de construcciones vecinas o accidentes topográficos) and naming the alternative 'calcular_sombras_hueco' for opening-level elements (voladizos, retranqueos, aleros). Nothing is left to inference.

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

Deploy Server