CE3X-MCP-Server

Overview Schema Source Related Servers Discussions Admin

Calcular Parametros Terciario Local Comercial

calcular_parametros_terciario_local_comercial

Read-onlyIdempotent

Calculates mandatory CE3X parameters for tertiary and commercial buildings, including lighting power, VEEI, RITE IDA ventilation rates, and occupancy based on CTE DB-HE3 and RITE.

Instructions

Estima los parámetros normativos obligatorios de CE3X para edificios de uso Terciario y Locales Comerciales: potencia de iluminación instalada (W/m²), VEEI, caudales de ventilación (RITE IDA) y tasa de ocupación según CTE DB-HE3 y RITE.

Cuándo usar: Invoque esta herramienta obligatoriamente cuando el edificio o inmueble certificado sea de uso terciario o local comercial para obtener los parámetros de iluminación y ventilación que exige CE3X en terciario.

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	Default
`tipo_actividad`	Yes	Tipo de actividad del local o edificio terciario (ej. 'Comercial', 'Oficinas', 'Docente', 'Restauracion', 'Sanitario').
`tipo_luminaria`	No	Tecnología de iluminación principal: 'LED', 'Fluorescencia', 'Halogena', 'Incandescente'.	LED
`superficie_util_m2`	Yes	Superficie útil del local comercial en metros cuadrados (m²).
`nivel_iluminacion_lux`	No	Nivel medio de iluminancia mantenida en lux según exigencias de la actividad (CTE DB-HE3). Por defecto 500 lux.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 17, 2026
- removedInput schema / properties / nivel_iluminacion_lux / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- changedInput schema / properties / nivel_iluminacion_lux / default
```
Previous value: -nullNew value: +500
```
- addedInput schema / properties / nivel_iluminacion_lux / description
```
Added value: +"Nivel medio de iluminancia mantenida en lux según exigencias de la actividad (CTE DB-HE3). Por defecto 500 lux."
```
- addedInput schema / properties / nivel_iluminacion_lux / exclusiveMinimum
```
Added value: +0
```
- addedInput schema / properties / nivel_iluminacion_lux / type
```
Added value: +"number"
```
- removedInput schema / properties / superficie_util_m2 / default
```
Removed value: -100
```
- addedInput schema / properties / superficie_util_m2 / description
```
Added value: +"Superficie útil del local comercial en metros cuadrados (m²)."
```
- addedInput schema / properties / superficie_util_m2 / exclusiveMinimum
```
Added value: +0
```
- removedInput schema / properties / tipo_actividad / default
```
Removed value: -"Comercio"
```
- addedInput schema / properties / tipo_actividad / description
```
Added value: +"Tipo de actividad del local o edificio terciario (ej. 'Comercial', 'Oficinas', 'Docente', 'Restauracion', 'Sanitario')."
```
- addedInput schema / properties / tipo_luminaria / description
```
Added value: +"Tecnología de iluminación principal: 'LED', 'Fluorescencia', 'Halogena', 'Incandescente'."
```
- addedInput schema / required
```
Added value: +[
+  "tipo_actividad",
+  "superficie_util_m2"
+]
```
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 and idempotentHint, and the description's 'operación analítica de solo lectura... no modifica archivos ni registros locales' largely restates them. It does not add non-obvious behavior (assumptions, default fallbacks, error cases) beyond the safety profile.

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-loads the purpose, then separates 'Cuándo usar' and 'Comportamiento' into labeled sections, which makes scanning easy. Minor redundancy: the read-only statement repeats the annotations and the terciario/comercial scope is restated.

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 need not be explained, and the description covers purpose, trigger and safety, which is sufficient for this four-parameter calculator. Only the parameter-to-normative-table mapping is left implicit.

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 every parameter is already documented in the input schema. The description adds domain framing but no parameter-level semantics (e.g., how tipo_actividad maps to occupancy/VEEI tables) beyond what the schema provides. 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 ('Estima') and a precisely scoped resource (parámetros normativos obligatorios de CE3X para terciario y locales comerciales), enumerating the concrete outputs (potencia de iluminación, VEEI, caudales RITE IDA, tasa de ocupación). No sibling tool computes normative tertiary parameters, and the scope boundary against residential use makes it distinguishable.

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?

Gives an explicit trigger condition ('Invoque esta herramienta obligatoriamente cuando el edificio... sea de uso terciario o local comercial') and implicitly excludes non-tertiary cases. It stops short of naming an alternative tool for residential/in other cases, so it is a clear context without full routing.

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

Deploy Server