Skip to main content
Glama
jmcaamanog

CE3X-MCP-Server

by jmcaamanog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Determinar Zona Climatica

determinar_zona_climatica
Read-onlyIdempotent

Determines the official CTE DB-HE climate zone (e.g., C1, D3) from province, municipality, and altitude. Use it before estimating transmittances or energy ratings to set winter and summer climate severity.

Instructions

Determina la zona climática CTE DB-HE oficial (ej. C1, D3, A3, E1) en función de la provincia, municipio y altitud sobre el nivel del mar según las tablas oficiales del Código Técnico de la Edificación (Apéndice B).

Cuándo usar: Invoque esta herramienta de forma obligatoria antes de estimar transmitancias o calcular la calificación energética para fijar la severidad climática de invierno y verano del emplazamiento.

Comportamiento y efectos secundarios: Operación analítica de solo lectura (Read-Only). No requiere conexión con CE3X ni modifica archivos en disco.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
altitud_mNoAltitud del inmueble sobre el nivel del mar en metros (m). Por defecto 0.0.
municipioYesNombre oficial del municipio correspondiente a la provincia.
provinciaYesNombre oficial de la provincia española (ej. 'Madrid', 'A Coruña', 'Sevilla', 'Barcelona').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / altitud_m / description
      Added value: +"Altitud del inmueble sobre el nivel del mar en metros (m). Por defecto 0.0."
    • addedInput schema / properties / altitud_m / maximum
      Added value: +4000
    • addedInput schema / properties / altitud_m / minimum
      Added value: +-50
    • addedInput schema / properties / municipio / description
      Added value: +"Nombre oficial del municipio correspondiente a la provincia."
    • addedInput schema / properties / provincia / description
      Added value: +"Nombre oficial de la provincia española (ej. 'Madrid', 'A Coruña', 'Sevilla', 'Barcelona')."
  2. First observedv1.5.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds genuinely new context: it is analytical, requires no CE3X connection, and does not write to disk, which tells the agent it can be called standalone.

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 purpose and then cleanly sectioned into usage and side effects; every sentence earns its place. The header labels add slight overhead but improve scanability for an agent.

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?

A simple three-parameter lookup with full schema coverage and an output schema that already documents the returned climate zone. The description covers purpose, timing, and side effects, so nothing needed to call it correctly is missing.

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 provincia, municipio, and altitud_m. The description only restates that these three inputs drive the lookup, adding no syntax, format, or lookup-behavior detail beyond the schema. 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 (Determina), the exact resource (zona climática CTE DB-HE oficial), and gives concrete example outputs (C1, D3, A3, E1). It also pins the authority (Apéndice B del CTE), so an agent can distinguish it from the many other calculation siblings without opening the schema.

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 is explicit: invoke mandatorily before estimating transmittances or computing the energy rating, to fix winter/summer climate severity. Clear context, though no alternatives or when-not conditions are named.

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