Skip to main content
Glama

calcular_retencion_alquiler

Read-only

Estima de forma rápida el IRPF del propietario por alquilar un inmueble: rendimiento neto, reducción del 50% por vivienda habitual (Ley 12/2023, vigente desde 2024) y la retención del 19% que practica el arrendatario cuando es empresa o profesional. Para el cálculo detallado con todas las reducciones de la Ley de Vivienda usa "calcular_rendimiento_capital_inmobiliario".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ibiNoIBI anual en euros. Por defecto 0.
seguroNoSeguro de hogar anual en euros. Por defecto 0.
comunidadNoGastos de comunidad anuales en euros. Por defecto 0.
otros_gastosNoOtros gastos deducibles (gestoría, publicidad...), en euros. Por defecto 0.
reparacionesNoReparación y conservación anual en euros. Por defecto 0.
precio_compraNoPrecio de compra del inmueble en euros (para la amortización del 3% del 70% del valor). Por defecto 0.
otros_ingresosNoOtros ingresos anuales del propietario, en euros (para estimar el tipo marginal). Por defecto 0.
alquiler_mensualYesAlquiler mensual bruto en euros
meses_alquiladosNoMeses alquilados al año. Por defecto 12.
intereses_hipotecaNoIntereses de hipoteca pagados en el año, en euros. Por defecto 0.
arrendatario_empresaNo¿El arrendatario es empresa o profesional? Si es true, aplica retención del 19%. Por defecto false.

TDQS

A4.4/5.0
Behavior4/5

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

Consistent with readOnlyHint; adds context about specific percentages and tax law (Ley 12/2023). No contradictions. Provides useful behavioral details beyond annotations.

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?

Two sentences, front-loaded with key information, no redundancy. Every word adds value.

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?

Given 11 parameters and no output schema, the description lists expected outputs (net income, reduction, withholding). Lacks output format but sufficient for a quick estimation tool.

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 baseline is 3. The description does not add meaning to individual parameters beyond the schema, but the schema itself is descriptive.

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 estimates IRPF for rental property, specifying net income, 50% reduction, and 19% withholding. It distinguishes from a sibling tool 'calcular_rendimiento_capital_inmobiliario' for detailed calculations.

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 directs to use 'calcular_rendimiento_capital_inmobiliario' for detailed calculations, providing clear when-not-to-use guidance. The description implies this is for quick estimates.

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