Skip to main content
Glama

Aurio Calculators

Simular hipoteca o préstamo

simular_hipoteca
Read-onlyIdempotent

Simula una hipoteca o un préstamo (sistema francés): cuota mensual, intereses totales, coste total y resumen año a año. Úsala para “cuánto pagaré de hipoteca”, “cuota mensual de la hipoteca”, “simular hipoteca de 200.000 € a 30 años”, “cuánto pago al mes por un préstamo de 15.000 €”, “cuántos intereses pago”. English: mortgage/loan calculator (monthly payment, total interest) for Spain, amounts in EUR.

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": {
      "importe": "<importe>",
      "interesAnual": "<interesAnual>"
    },
    "name": "simular_hipoteca"
  }
}

Input Schema

NameRequiredDescriptionDefault
aniosNoPlazo en años (hipoteca). Term in years. Usa `meses` si te lo dan en meses.
mesesNoPlazo en meses (préstamos). Term in months; si viene, manda sobre `anios`.
importeYesImporte del préstamo o hipoteca en euros (capital pedido). Loan amount in EUR.
interesAnualYesTipo de interés nominal anual en %, p. ej. 2.9 para un 2,9 %. Annual interest rate in %.

Output Schema

NameRequiredDescriptionDefault
ctaYes
kindYes
mesesYes
importeYes
costeTotalYes
disclaimerYes
cuotaMensualYes
resumenAnualYes
interesAnualPctYes
interesesTotalesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the amortization method (French system), the complete set of computed outputs including a year-by-year breakdown, and the domain/currency constraint (Spain, EUR).

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?

Front-loaded with the core purpose and outputs, then usage examples, then an English restatement for bilingual robustness. The long run of quoted example phrases is somewhat repetitive, but each line is short and scannable rather than wasteful.

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?

An output schema exists, so return values need not be detailed, and the description still summarizes them. The main residual ambiguity for a financial calculator is whether 'coste total' includes taxes, fees or insurance, which is left unstated; otherwise the domain, currency and term units are all covered.

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%, and the schema already explains every field including the precedence rule ('si viene, manda sobre `anios`' for meses). The description adds no parameter-level meaning beyond that, so the baseline of 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?

States a specific verb and resource ('Simula una hipoteca o un préstamo') plus the calculation method (sistema francés) and the exact outputs produced (cuota mensual, intereses totales, coste total, resumen año a año). This clearly separates it from siblings like simular_ahorro, calcular_modelo_130 or estimar_renta, which handle savings and tax rather than loan amortization.

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 quoted user phrasings ('cuánto pagaré de hipoteca', 'cuánto pago al mes por un préstamo de 15.000 €') give an agent concrete trigger conditions, which is stronger than implied usage. It stops short of explicit exclusions — notably it never says when to prefer the sibling me_lo_puedo_permitir (affordability) over this pure payment calculation.

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