Skip to main content
Glama

Comprar casa en UK: impuestos e hipoteca

calcular_vivienda
Read-onlyIdempotent

Calcula el impuesto de compra de vivienda según el país (Stamp Duty en Inglaterra e Irlanda del Norte, LBTT en Escocia, LTT en Gales), con primera vivienda, segunda vivienda o comprador no residente. Si das entrada e interés, añade la cuota mensual de la hipoteca, el dinero inicial y la diferencia con tu alquiler. Solo números: no recomienda hipotecas.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "precio": "<precio>"
    },
    "name": "calcular_vivienda"
  }
}

Input Schema

NameRequiredDescriptionDefault
anosNoPlazo de la hipoteca en años.
paisNoDónde está la vivienda.inglaterra
precioYesPrecio de la vivienda en libras.
entradaNoOpcional. Entrada (deposit) en libras.
interesNoOpcional. Tipo de interés anual de la hipoteca, en %.
adicionalNoYa tienes otra vivienda (segunda vivienda o inversión).
no_residenteNoNo resides en UK (recargo en Inglaterra e Irlanda del Norte).
alquiler_mensualNoOpcional. Lo que pagas de alquiler al mes, para comparar.
primera_viviendaNoComprador de primera vivienda (first-time buyer).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation. The description adds useful behavioral detail beyond that: it explains which tax regime applies by country, which buyer statuses affect the calculation, and that extra mortgage outputs appear only when deposit and interest are provided. It also sets the boundary that the tool does not recommend mortgages.

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 three tight sentences, front-loads the core calculation, then covers optional mortgage outputs and the advisory boundary. Every sentence adds useful information, and there is no repetition of schema-level parameter descriptions.

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 9-parameter calculator with no output schema, the description explains the main tax calculation, the country-specific regimes, optional mortgage outputs and the rental comparison. It is mostly complete, though without an output schema an agent still has to infer the exact return structure for the tax amount and mortgage breakdown.

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 the baseline is 3, but the description adds meaning beyond the individual parameter descriptions by grouping country into tax regimes, linking buyer-status flags to first-home/second-home/non-resident treatment, and explaining that deposit and interest trigger mortgage outputs. It does not mention the loan term parameter explicitly, but the schema already documents that field.

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 states a specific verb and resource: it calculates UK home purchase tax by country, including Stamp Duty, LBTT and LTT, plus optional mortgage figures. It also distinguishes the tool from advisory mortgage tools by saying 'Solo números: no recomienda hipotecas.' An agent can tell exactly what domain this calculator covers compared with siblings like calcular_isa or calcular_nomina.

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

Usage Guidelines4/5

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

The description gives clear context for when the tool applies: UK home purchase tax calculations, with first-time, second-home or non-resident buyer modes, and optional mortgage comparison when deposit and interest are supplied. It does not explicitly name alternative sibling tools or state when not to use this calculator, but the domain and conditional usage are clear.

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.

Resources