Skip to main content
Glama
jmcaamanog

CE3X-MCP-Server

by jmcaamanog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Registrar Ensayo Estanqueidad Blower Door

registrar_ensayo_estanqueidad_blower_door
Read-onlyIdempotent

Calculates n50, q50, and CE3X air infiltration rate from Blower Door airtightness test data, replacing default estimates with measured values.

Instructions

Procesa un ensayo de estanqueidad al aire según norma UNE-EN ISO 9972 (Blower Door), calculando la tasa de renovación n50 (renovaciones/hora), la permeabilidad q50 (m³/h·m²) y la tasa de infiltración de aire para CE3X.

Cuándo usar: Utilice esta herramienta cuando se haya ejecutado un ensayo de presurización/despresurización Blower Door para sustituir la tasa de infiltración estimada por defecto de CE3X por el valor real medido.

Comportamiento y efectos secundarios: Operación de cálculo analítico normativo (Read-Only). No altera archivos ni estado persistente.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caudal_50pa_m3hYesCaudal de fuga de aire medido a 50 Pa de presión en metros cúbicos por hora (m³/h).
volumen_neto_m3YesVolumen interno neto del espacio calefactado en metros cúbicos (m³).
superficie_envolvente_m2YesSuperficie total de la envolvente térmica interior en metros cuadrados (m²).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / caudal_50pa_m3h / description
      Added value: +"Caudal de fuga de aire medido a 50 Pa de presión en metros cúbicos por hora (m³/h)."
    • addedInput schema / properties / caudal_50pa_m3h / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / superficie_envolvente_m2 / description
      Added value: +"Superficie total de la envolvente térmica interior en metros cuadrados (m²)."
    • addedInput schema / properties / superficie_envolvente_m2 / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / volumen_neto_m3 / description
      Added value: +"Volumen interno neto del espacio calefactado en metros cúbicos (m³)."
    • addedInput schema / properties / volumen_neto_m3 / exclusiveMinimum
      Added value: +0
  2. First observedv1.5.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description largely restates this ('Read-Only', 'no altera archivos ni estado persistente'). It does add value by naming the normative calculation basis (UNE-EN ISO 9972) and the derived quantities, but says nothing about edge cases such as validation of the 50 Pa measurement or handling of degenerate geometry.

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?

Well front-loaded with labeled sections (Cuándo usar, Comportamiento y efectos secundarios) and no filler sentences. Minor redundancy between 'Read-Only' and 'no altera archivos ni estado persistente', which say the same thing twice.

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, the description needn't explain return values, and it correctly covers purpose, trigger condition, and safe behavior. Complete enough for a 3-parameter read-only calculation tool, though it omits any note on input validity ranges or expected output units.

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% and all three required numeric parameters are documented with units and exclusiveMinimum constraints. The description mentions the computed outputs but does not map them back to the inputs or add format guidance beyond the schema, so the schema does the heavy lifting.

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 (procesa/calcula) and resource (ensayo de estanqueidad al aire Blower Door bajo UNE-EN ISO 9972), and names the exact outputs produced: n50, q50 y tasa de infiltración para CE3X. This clearly distinguishes it from the sibling registrar_ensayo_flujometria_termica_in_situ, which is a different test.

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' block gives an explicit trigger condition: use it after a Blower Door pressurization/depressurization test to replace CE3X's default infiltration rate with the measured value. It lacks any explicit exclusion or named alternative for when a test has not been run, but the context is clear.

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

Deploy Server

Other Tools