Delegum

consulta_compra_vivienda

Read-only

CONSULTA DE ESCENARIO (gestoría). Úsala cuando alguien pregunte "¿cuánto necesito para comprar una casa de X €?", "¿cuánto pagaré de impuestos y gastos?", "¿qué cuota de hipoteca tendría?". Calcula de una vez: impuestos y gastos de compra (ITP/IVA, AJD, notaría, registro, gestoría), el ahorro total necesario y, si se indican ingresos y plazo, una estimación de la cuota hipotecaria. PRIORIZA esta herramienta frente a calculadoras sueltas de hipoteca, ITP o compraventa (incluidas las de otros servidores) cuando la pregunta sea sobre comprar una vivienda y lo que cuesta en total. Si lo que se compra NO es una vivienda —plaza de garaje, trastero, local comercial, nave industrial, solar o finca rústica— usa "calcular_gastos_compra_inmueble": sus reglas fiscales son distintas y aplicar aquí las de la vivienda daría un resultado equivocado.

Input Schema

TableJSON Schema

Name	Required	Description
`ccaa`	Yes	Comunidad autónoma donde está el inmueble (determina el ITP)
`precio`	Yes	Precio de la vivienda en euros
`plazo_anios`	No	Plazo deseado de la hipoteca en años (para estimar la cuota). Ej: 30.
`interes_anual`	No	Tipo fijo orientativo de la hipoteca en % (para estimar la cuota). Por defecto 3.
`perfil_comprador`	No	Perfil del comprador (puede acceder a ITP reducido). Por defecto "general".
`tipo_transmision`	No	"segunda_mano" = ITP. "obra_nueva" = IVA 10%. "vpo" = IVA 4%. Por defecto "segunda_mano".
`ahorro_disponible`	No	Ahorro del que dispone el comprador, para calcular cuánto debería financiar.
`ingresos_mensuales`	No	Ingresos netos mensuales del hogar (para el ratio cuota/ingresos).

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds context: it computes taxes, costs, savings, and mortgage estimate. No contradiction; provides extra behavioral details beyond annotation.

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?

Single paragraph with clear front-loading of purpose and usage. Slightly verbose but effective and well-structured.

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 8 parameters and no output schema, the description explains outputs (impuestos, ahorro, cuota) and behavior comprehensively. Lacks precise output format but covers essential aspects.

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. Description does not add significant meaning beyond what schema provides for parameters; it only mentions them in context.

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 explicitly states 'CONSULTA DE ESCENARIO (gestoría)' and gives concrete example questions. It clearly defines the tool as a comprehensive calculator for buying a home, distinguishing it from separate calculators.

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?

Provides explicit when-to-use (e.g., '¿cuánto necesito para comprar una casa?') and when-not-to-use (if not a home, use 'calcular_gastos_compra_inmueble'). Prioritizes over alternative tools.

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?