Skip to main content
Glama

mireforma.net

Validar plano con la normativa

reforma_validate_plan
Read-onlyIdempotent

Check a renovation floor plan against local building rules (CTE, regional habitability, local bylaws) and explain the permit process. Guidance only.

Comprueba un plano de reforma contra la normativa del municipio (CTE, habitabilidad autonómica, ordenanza local) y devuelve los incumplimientos con su fuente oficial y el trámite paso a paso: licencia, declaración responsable o comunicación, documentos, ICIO, tasa y sede. plano sigue mireforma-plano/1 (GET /api/validar-plano/esquema) o es el JSON de Magicplan con formato magicplan-api; ejemplo usa un plano de muestra. Orientativo, no sustituye al técnico.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reforma_validate_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
ineNoCódigo INE del municipio, 5 dígitos
fechaNoFecha AAAA-MM-DD para la vigencia de las reglas
obrasNoObras: redistribucion_parcial, reforma_bano, estructura_puntual, cambio_ventanas…
planoNoPlano mireforma-plano/1 o JSON de Magicplan
detalleNoresumen omite lo que cumple
ejemploNoId de un plano de ejemplo, p. ej. bcn_piso_redistribucion
ficheroNoFichero de plano: CSV de Magicplan (room list), IFC o DXF ASCII, en base64 o texto. Máx. 20 MB
formatoNoFormato del plano o del fichero; si falta se deduce de la extensión
pem_eurNoPresupuesto de ejecución material para estimar el ICIO
altura_mNoAltura libre para un DXF 2D
edificioNoanio_construccion, protegido, en_conjunto_historico, suelo, altitud_m, planta

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower. Beyond them the description discloses the output semantics (non-compliance findings with official sources, permit route, documents, ICIO, fee, office) and an important limitation, that results are advisory and do not replace a qualified technician — real value for an agent deciding how much to trust the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is well front-loaded — purpose first, then outputs, then input formats, then the advisory caveat. The cost is bilingual duplication: the same information is delivered in English and Spanish, roughly doubling length without adding content for a single-language reader.

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 an 11-parameter tool with nested objects and no output schema, the description does a good job covering what is returned (findings with sources plus step-by-step permit procedure) and the advisory framing. It does not say whether at least one of plano/fichero/ejemplo must be supplied, which is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds value by clarifying that 'plano' accepts either mireforma-plano/1 or Magicplan JSON, that 'ejemplo' refers to a sample plan, and by pointing to GET /api/validar-plano/esquema for the full format spec. That pointer is information the schema does not carry, lifting it above baseline.

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?

The description names a specific verb and resource ('Check a renovation floor plan against local building rules') and enumerates the rule sets (CTE, regional habitability, local bylaws). It also states the output shape: incumplimientos with official source plus the permit process steps. No sibling in the catalog does validation, so the tool is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: it is framed as an advisory check ('Guidance only', 'Orientativo, no sustituye al técnico') and the return contents are described, which tells the agent when the output is useful. However, there is no explicit when-to-use vs. when-not guidance, no prerequisites (e.g. needing an INE code or an ejemplo id to proceed), and no named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources