Skip to main content
Glama

calcular_rendimiento_capital_inmobiliario

Read-only

Calcula el rendimiento neto del alquiler que se declara en el IRPF (capital inmobiliario). Deduce todos los gastos permitidos (intereses, IBI, seguros, reparaciones —con límite—, comunidad, administración y amortización del 3%) y aplica la reducción que corresponda según la Ley de Vivienda: 90% (zona tensionada + bajada ≥5%), 70% (zona tensionada nueva/vulnerable), 60% (rehabilitación) o 50% (vivienda habitual general). Es la versión detallada para la declaración; para una estimación rápida con la retención del 19% usa "calcular_retencion_alquiler".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
otrosNoOtros gastos necesarios (€/año)
segurosNoPrimas de seguros del inmueble (€/año)
comunidadNoCuotas de la comunidad de propietarios (€/año)
tipo_inmuebleYesTipo de inmueble y reducción aplicable: vivienda_habitual_arrendatario=50%, vivienda_zona_tensionada_nueva=70%, vivienda_rehabilitada=60%, vivienda_tension_reduccion_5pct=90%, no_vivienda=local/garaje (sin reducción)
administracionNoGastos de administración y gestión: agencia, administrador (€/año)
ibi_y_tributosNoIBI, tasa de basuras y tributos locales (€/año)
ingresos_integrosYesIngresos íntegros del arrendamiento en el ejercicio, en euros
intereses_prestamoNoIntereses del préstamo hipotecario del inmueble (€/año)
valor_construccionNoValor de construcción del inmueble (€) para calcular la amortización al 3%
reparacion_conservacionNoReparación y conservación, NO mejoras (€/año)

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true. The description adds rich behavioral context: it deducts allowed expenses with limits, applies reductions per housing law, and is a calculation with no side effects. 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.

Conciseness5/5

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

The description is two sentences, front-loaded with the main purpose and packed with necessary details. No redundant information; the sibling reference is placed at the end appropriately.

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 complex tool with 10 parameters and no output schema, the description covers the core logic and reductions. However, it lacks explicit mention of the return value format and the specific limit on repairs, which could be important for an AI agent.

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%, so baseline is 3. The description adds meaning by explaining the enum values for 'tipo_inmueble' and the context of deductions, which goes beyond the schema descriptions. However, it could have elaborated on the 'reparacion_conservacion' limit.

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 clearly states it calculates net rental yield for IRPF (capital inmobiliario), specifying deductions and reductions. The verb 'calcula' and resource 'rendimiento neto del alquiler' are specific, and it distinguishes from the sibling 'calcular_retencion_alquiler'.

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?

The description explicitly says when to use this tool (detailed version for declaration) and when to use an alternative ('calcular_retencion_alquiler' for quick estimate with 19% withholding), providing clear guidance.

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