Skip to main content
Glama

mireforma.net

Calcular presupuesto de reforma

reforma_estimate_budget
Read-onlyIdempotent

Estimate a renovation budget per room (type and m²) with official manufacturer prices, labour, VAT and local ICIO tax.

Presupuesto de una reforma por embudo de decisiones, sin cuenta. Nivel 1: estancias con tipo (bano, cocina, dormitorio, salon, paso, trabajo, servicio) y m² → cantidades y rango bajo/medio/alto. Nivel 2: en elecciones por concepto (inodoro, lavabo, grifo-lavabo, grifo-ducha, plato-ducha, electricidad, solado…) pasa marca o ref del catálogo; si no, se asume la opción más barata que cumple. Nivel 3: precio_proveedor fija el precio de un proveedor. Devuelve líneas con material (tarifa del fabricante con tipo de precio, vigencia y enlace oficial) y mano de obra con fuente, PEM, IVA (10 %/21 %), ICIO del municipio (ine) y tasa en texto. formato csv devuelve CSV. Orientativo, no es una oferta.

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_estimate_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
m2NoAtajo para una estancia: superficie en m²
ineNoMunicipio: código INE de 5 dígitos o nombre
tipoNoAtajo para una estancia: tipo
formatoNo
estanciasNoEstancias; sin partidas se usa la plantilla del tipo
materialesNoQuién compra los materiales (afecta al IVA)
vivienda_mas_2_aniosNofalse si la vivienda tiene menos de dos años (IVA 21 %)

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 cover the safety profile (readOnlyHint, idempotent, non-destructive), and the description still adds real behavior: default fallback selection when no brand/ref is given, VAT logic tied to materiales and vivienda_mas_2_anios (10%/21%), ICIO from the municipality, CSV via formato, and the caveat 'Orientativo, no es una oferta'. It does not describe error behavior when an INE code or catalogue ref is unknown.

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?

Information is front-loaded with a one-sentence English summary before the detailed Spanish body, which reads well. The cost is duplication between the English opener and the Spanish restatement, and the dense run-on enumeration of example concepts. Most sentences carry load, so it is long but not padded.

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 a read-only estimator with 7 parameters, no output schema and nested-but-simple inputs, the description covers the decision funnel, the returned line structure (material with tariff/vigencia/link, labour with source, PEM, IVA, ICIO) and the orientative disclaimer. Missing pieces are modest: no guidance on what happens with unresolvable refs or on how detailed 'partidas' should be.

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 coverage is already 86%, so baseline is 3, but the description adds meaning the schema lacks — notably the allowed 'tipo' values (bano, cocina, dormitorio, salon, paso, trabajo, servicio), which the schema types as a bare string, plus the notion that estancias without partidas fall back to a per-type template. The m²/tipo shortcuts are mentioned only as 'Atajo para una estancia', leaving their interaction with estancias implicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a precise verb and resource: 'Estimate a renovation budget per room (type and m²)' and names the cost components (manufacturer prices, labour, VAT, ICIO). The three-level escalation (estancias → elecciones → precio_proveedor) makes the tool's scope easy to grasp. It never names a sibling such as reforma_budget_options, so it stops short of the sibling differentiation a 5 requires.

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 description spells out a progressive usage path: level 1 you pass rooms with type and m², level 2 you pass brand/ref per concept and 'si no, se asume la opción más barata que cumple', level 3 you pin a supplier price. That is clear invocation context. It does not say when to prefer a sibling tool or what input combinations are invalid.

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