CE3X-MCP-Server

Overview Schema Source Related Servers Discussions Admin

Registrar Ensayo Flujometria Termica In Situ

registrar_ensayo_flujometria_termica_in_situ

Read-onlyIdempotent

Registers an in-situ heat flux meter test to calculate real thermal transmittance (U) and resistance (R) per ISO 9869-1 for CE3X input.

Instructions

Registra formalmente un ensayo in situ de flujometría térmica con termoflujómetro y sondas de temperatura según norma ISO 9869-1, calculando la transmitancia térmica real U (W/m²K) y la resistencia térmica R del cerramiento.

Cuándo usar: Utilice esta herramienta cuando se hayan realizado mediciones directas in situ con termoflujómetro para acreditar la transmitancia real de un muro histórico sin necesidad de estimarlo por defecto.

Comportamiento y efectos secundarios: Operación analítica de cálculo normativo (Read-Only). Devuelve el valor oficial de U para su inserción como valor conocido en CE3X.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`flujo_medio_w_m2`	Yes	Densidad de flujo de calor media medida a través del cerramiento en vatios por metro cuadrado (W/m²).
`elemento_analizado`	No	Descripción del cerramiento ensayado (ej. 'Muro de fachada de ladrillo visto').	Muro de fachada exterior
`duracion_ensayo_horas`	No	Duración total del registro continuo en horas (mínimo 72 h según ISO 9869-1).
`temp_exterior_media_c`	Yes	Temperatura media del aire exterior durante el ensayo en grados Celsius (°C).
`temp_interior_media_c`	Yes	Temperatura media del aire interior durante el ensayo en grados Celsius (°C).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 17, 2026

addedInput schema / properties / duracion_ensayo_horas / description

Added value: +"Duración total del registro continuo en horas (mínimo 72 h según ISO 9869-1)."

addedInput schema / properties / duracion_ensayo_horas / minimum
```
Added value: +24
```

changedInput schema / properties / elemento_analizado / default

Previous value: -"Fachada principal"New value: +"Muro de fachada exterior"

addedInput schema / properties / elemento_analizado / description

Added value: +"Descripción del cerramiento ensayado (ej. 'Muro de fachada de ladrillo visto')."

addedInput schema / properties / flujo_medio_w_m2 / description

Added value: +"Densidad de flujo de calor media medida a través del cerramiento en vatios por metro cuadrado (W/m²)."

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

addedInput schema / properties / temp_exterior_media_c / description

Added value: +"Temperatura media del aire exterior durante el ensayo en grados Celsius (°C)."

addedInput schema / properties / temp_interior_media_c / description

Added value: +"Temperatura media del aire interior durante el ensayo en grados Celsius (°C)."

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, and the description usefully reinforces that 'registrar' is an analytical normative calculation rather than a persistence write, plus states the output's purpose (official U for insertion into CE3X). It adds context beyond the annotations, though it does not discuss assumptions or limits of the calculation.

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 with the core purpose, then organized under clear 'Cuándo usar' and 'Comportamiento' headers. Slightly verbose but every section carries information; no filler sentences.

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 needn't be described, and annotations cover the safety profile. The description supplies purpose, precondition, and behavioral framing, leaving only minor gaps such as handling of invalid or short measurement windows.

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, including units, defaults, and the 72 h ISO minimum. The description adds no parameter-level syntax or format detail beyond what the schema provides, so 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 (Registra/calcula) and resource (ensayo in situ de flujometría térmica con termoflujómetro y sondas), naming the governing standard ISO 9869-1 and the outputs U and R. It is clearly distinguishable from siblings like registrar_ensayo_estanqueidad_blower_door and estimar_envolvente_por_defecto.

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 an explicit precondition: direct in-situ measurements with a heat flow meter to certify a historic wall's real transmittance. It implicitly contrasts with the default-estimation path ('sin necesidad de estimarlo por defecto') but never names the sibling tool, so it stops short of full routing guidance.

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

Deploy Server