Delegum

calcular_capacidad_hipoteca

Read-only

Estima el préstamo hipotecario máximo que un hogar puede asumir de forma sostenible aplicando la regla del Banco de España (esfuerzo ≤ 30-35% de los ingresos netos). Devuelve el capital máximo financiable, el precio máximo de vivienda, la entrada disponible y el % de financiación. Para el detalle de la cuota usa "calcular_hipoteca"; para una compra completa con impuestos usa "consulta_compra_vivienda".

Input Schema

TableJSON Schema

Name	Required	Description
`plazo`	No	Plazo de la hipoteca en años. Por defecto 30.
`tasa_interes`	No	Tipo de interés de la simulación en %. Por defecto 3,5.
`umbral_esfuerzo`	No	Umbral máximo de esfuerzo en % (BdE recomienda ≤30). Por defecto 30.
`ahorros_disponibles`	Yes	Ahorros disponibles para la entrada, en euros
`otras_deudas_mensuales`	No	Otras cuotas de deuda ya existentes (coche, préstamo personal...), en euros/mes. Por defecto 0.
`ingresos_mensuales_netos`	Yes	Ingresos netos mensuales del hogar (todos los miembros), en euros

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already include readOnlyHint=true. The description adds context by explaining the calculation rule and outputs. No contradictions; the description enhances understanding without repeating the annotation.

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 with clear front-loading of purpose, followed by output list and sibling tool references. No wasted words, and the structure is easy to parse.

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

Completeness5/5

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

With no output schema, the description fully covers the return values: maximum capital, max price, available down payment, and financing percentage. It also explains the rule and gives sibling tool context, making it complete for a calculator 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 coverage is 100% with descriptions for all 6 parameters. The description restates default values and the effort threshold but does not add significant new meaning beyond the schema. Baseline 3 applies.

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 the tool estimates the maximum mortgage using the Bank of Spain rule (esfuerzo ≤ 30-35%). It specifies the returned values and distinguishes from siblings like 'calcular_hipoteca' and 'consulta_compra_vivienda'.

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 advises when to use this tool vs alternatives: for monthly payment details use 'calcular_hipoteca', for a complete purchase with taxes use 'consulta_compra_vivienda'. This provides clear context for agent decision-making.

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

All Delegum tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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

Need Help?