Skip to main content
Glama

calcular_gastos_compra_inmueble

Read-only

Calcula los impuestos y gastos de comprar un inmueble que NO es una vivienda: plaza de garaje, trastero, local comercial, nave industrial, solar edificable o finca rústica. Úsala cuando la pregunta sea "¿cuánto cuesta comprar un garaje/local/nave/terreno en X?", "¿qué impuestos pago al comprar una parcela?" o "¿ITP o IVA en la compra de un local?". Cada tipo tiene su propia regla: el garaje o trastero independiente no lleva el IVA reducido del anejo, el local y la nave admiten la renuncia a la exención de IVA, el solar depende de si vende un promotor o un particular, y la finca rústica está exenta de IVA y no genera plusvalía municipal. Para una vivienda usa "consulta_compra_vivienda", que además estima la hipoteca y el ahorro necesario.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccaaYesComunidad autónoma donde está el inmueble (determina el ITP)
precioYesPrecio de compra del inmueble en euros
gestoriaNoGastos de gestoría en euros. Por defecto 500.
obra_nuevaNotrue = primera entrega del promotor (tributa por IVA). false o ausente = segunda mano (tributa por ITP salvo renuncia a la exención).
tipo_inmuebleYesTipo de inmueble. "solar_edificable" = terreno urbano donde se puede construir; "finca_rustica" = suelo rústico o agrario, exento de IVA.
perfil_compradorNoPerfil del comprador. Solo produce efecto en vivienda y en anejos comprados con ella: los tipos reducidos de ITP son exclusivos de la vivienda habitual.
anejo_de_viviendaNoSolo para garaje y trastero: true si se compra JUNTO con la vivienda como anejo (IVA reducido 10% en obra nueva), false si se compra por separado (IVA 21%). Por defecto true.
renuncia_exencion_ivaNoSolo para local, nave y finca rústica en segunda mano: true si el vendedor renuncia a la exención de IVA (art. 20.Dos LIVA). Exige que ambas partes sean empresarios o profesionales con derecho a deducción. La operación pasa de ITP a IVA con inversión del sujeto pasivo.
vendedor_es_empresarioNoSolo para solar edificable: true si vende un promotor o empresario (IVA 21% + AJD), false si vende un particular (ITP). Por defecto false.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true; description adds value by explaining no modification occurs and detailing tax rules (e.g., finca rústica exempt from IVA and plusvalía). No contradiction.

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 purpose and usage; second part details rules per type. Some redundancy could be trimmed, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, and description does not explain what the tool returns (e.g., breakdown of taxes, total cost). For a calculation tool, this is a notable 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 coverage is 100% (baseline 3). Description adds meaning by explaining when parameters apply (e.g., anejo_de_vivienda only for garaje/trastero, renuncia_exencion_iva for local/nave/rústica) and their tax implications.

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?

Description clearly states verb 'calcula' and resource 'impuestos y gastos de comprar un inmueble que NO es una vivienda', listing specific types (garaje, local, etc.). It distinguishes from sibling by naming 'consulta_compra_vivienda' for houses.

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

Usage Guidelines5/5

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

Explicitly says when to use ('cuando la pregunta sea...') and when not ('Para una vivienda usa consulta_compra_vivienda'). Provides usage rules per property type.

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.

TDQS

A3.9/5.0
Disambiguation3/5

There are many tools with overlapping domains (e.g., multiple retirement calculators, home buying calculators), but detailed descriptions and explicit guidance on when to use comprehensive vs. specific tools help clarify. However, the sheer number (49) still creates potential confusion for an agent.

Naming Consistency5/5

All tools follow a consistent convention: infinitive verb or noun prefix (calcular, comparar, consulta) followed by descriptive noun phrase in snake_case. No mixed styles or irregularities.

Tool Count3/5

49 tools is high but justifiable given the broad scope of Spanish financial/legal calculations. It leans toward the heavy side but remains within a manageable range for a comprehensive server.

Completeness4/5

The tool set covers a wide spectrum of personal finance: income, taxes, housing, inheritance, self-employment, investments, etc. Only minor gaps exist (e.g., no separate tool for rental income beyond the alquiler tools, but included in IRPF).

Resources