CE3X-MCP-Server

Overview Schema Source Related Servers Discussions Admin

Calcular Transmitancia Ventana Iso10077

calcular_transmitancia_ventana_iso10077

Read-onlyIdempotent

Calculate a window's total thermal transmittance (Uw) per ISO 10077-1, weighting glass and frame areas and including the spacer effect. Use it to get accurate glazing values for CE3X envelopes.

Instructions

Calcula la transmitancia térmica total Uw (W/m²K) de una ventana conforme a la norma UNE-EN ISO 10077-1, ponderando las áreas de vidrio y marco e incorporando el efecto del intercalario térmico.

Cuándo usar: Utilice esta herramienta para calcular con precisión la transmitancia de huecos acristalados a partir de los datos técnicos de marco y vidrio antes de introducirlos en la envolvente térmica de CE3X.

Comportamiento y efectos secundarios: Operación analítica de solo lectura (Read-Only). No altera archivos ni estado local.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`alto_m`	Yes	Alto del hueco de ventana en metros (m).
`ancho_m`	Yes	Ancho del hueco de ventana en metros (m).
`u_marco_w_m2k`	Yes	Transmitancia térmica del marco Uf en W/m²K (ej. 5.7 para metálico sin RPT, 3.2 con RPT, 2.2 para madera, 1.8 para PVC).
`fraccion_marco`	No	Fracción de superficie ocupada por el marco respecto al hueco total (0.10 a 0.50). Por defecto 0.20 (20%).
`u_vidrio_w_m2k`	Yes	Transmitancia térmica del vidrio Ug en W/m²K (ej. 5.7 para simple, 2.8 para doble estándar, 1.1 para bajo emisivo).
`tipo_intercalario`	No	Tipo de espaciador o intercalario del doble acristalamiento: 'aluminio' o 'calido_warm_edge'.	aluminio

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 / alto_m / description
```
Added value: +"Alto del hueco de ventana en metros (m)."
```
- addedInput schema / properties / alto_m / exclusiveMinimum
```
Added value: +0
```
- addedInput schema / properties / ancho_m / description
```
Added value: +"Ancho del hueco de ventana en metros (m)."
```
- addedInput schema / properties / ancho_m / exclusiveMinimum
```
Added value: +0
```
- changedInput schema / properties / fraccion_marco / default
```
Previous value: -0.25New value: +0.2
```
- addedInput schema / properties / fraccion_marco / description
```
Added value: +"Fracción de superficie ocupada por el marco respecto al hueco total (0.10 a 0.50). Por defecto 0.20 (20%)."
```
- addedInput schema / properties / fraccion_marco / maximum
```
Added value: +0.6
```
- addedInput schema / properties / fraccion_marco / minimum
```
Added value: +0.05
```
- changedInput schema / properties / tipo_intercalario / default
```
Previous value: -"termicamente_mejorado"New value: +"aluminio"
```
- addedInput schema / properties / tipo_intercalario / description
```
Added value: +"Tipo de espaciador o intercalario del doble acristalamiento: 'aluminio' o 'calido_warm_edge'."
```
- addedInput schema / properties / u_marco_w_m2k / description
```
Added value: +"Transmitancia térmica del marco Uf en W/m²K (ej. 5.7 para metálico sin RPT, 3.2 con RPT, 2.2 para madera, 1.8 para PVC)."
```
- addedInput schema / properties / u_marco_w_m2k / exclusiveMinimum
```
Added value: +0
```
- addedInput schema / properties / u_vidrio_w_m2k / description
```
Added value: +"Transmitancia térmica del vidrio Ug en W/m²K (ej. 5.7 para simple, 2.8 para doble estándar, 1.1 para bajo emisivo)."
```
- addedInput schema / properties / u_vidrio_w_m2k / exclusiveMinimum
```
Added value: +0
```
First observedv1.5.1Oct 17, 2026

TDQS

A3.9/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 essentially restates this ('Operación analítica de solo lectura... No altera archivos ni estado local') rather than adding new behavioral context. It discloses no validation limits (e.g. the 0.05–0.60 fraccion_marco bounds), error behavior, or robustness notes beyond what the annotations cover.

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?

Structure is front-loaded and scannable with labeled sections (Cuándo usar, Comportamiento y efectos secundarios). The effects sentence largely duplicates the annotations, so it is slightly less than maximal economy, but overall it is tight.

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?

For a pure calculation tool with a 6-parameter schema (4 required) and an output schema, the definition adequately conveys purpose, timing, and non-mutating nature; return values correctly need not be explained. It could add a note on valid input ranges or edge cases to be fully complete.

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 fully documents all six parameters (units, example values, defaults, range). The description adds conceptual framing of area weighting and the intercalario effect but no syntax or usage detail beyond the schema, 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?

States a specific verb (calcular) and resource (transmitancia térmica total Uw de una ventana) and grounds it in a named standard (UNE-EN ISO 10077-1), plus the method (weighting glass/marco areas, intercalario effect). It is clearly distinguishable from siblings like calcular_puentes_termicos or 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 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 concrete context: use it to obtain accurate glazing transmittance from frame/glass data before entering it into the CE3X thermal envelope. This is a clear usage context, but it names no explicit alternative tool or exclusion (e.g. when NOT to use it vs. other envelope calculators).

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

Deploy Server