Skip to main content
Glama

Nido Raíz — Inmuebles en Colombia

Calcular la cuota de un crédito hipotecario

calcular_financiacion
Read-onlyIdempotent

Calcula la cuota mensual, el monto financiable y la cuota inicial de un crédito hipotecario en Colombia, por amortización francesa y con tasa efectiva anual. Es una estimación ilustrativa, no una oferta de crédito.

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_financiacion"
  }
}

Input Schema

NameRequiredDescriptionDefault
aniosNoPlazo del crédito en años. Por defecto 15, que es lo habitual en Colombia
precioYesPrecio del inmueble en pesos colombianos
tasaEaPctNoTasa efectiva anual en porcentaje. Por defecto 13
cuotaInicialPctNoPorcentaje de cuota inicial. Por defecto 30

Output Schema

NameRequiredDescriptionDefault
estimacionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new context beyond them: the calculation method (French amortization with effective annual rate) and that the result is an illustrative estimate, not a credit offer. It stops short of noting that unspecified parameters fall back to defaults, which matters behaviorally.

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 tight sentences: the first front-loads what is computed and how, the second qualifies the output. No filler, no repetition of schema detail.

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 no explanation, and annotations cover the safety profile. The description supplies currency (pesos colombianos implicit in the domain), locale and method. The remaining gap is routing guidance against sibling tools such as evaluar_inversion, which a complete definition would address.

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%, with types, ranges and defaults documented for all four parameters, so the schema carries parameter meaning. The description adds only conceptual framing (tasa efectiva anual, monto financiable tied implicitly to cuotaInicialPct) without restating units or defaults. Baseline 3 is appropriate.

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 (calcula) plus three concrete outputs (cuota mensual, monto financiable, cuota inicial), the domain (crédito hipotecario en Colombia) and the method (amortización francesa, tasa efectiva anual). An agent can tell this is a mortgage payment estimator rather than a property search or visit-booking tool without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied by the purpose: estimate a mortgage installment given a property price. There is no explicit when-to-use versus the sibling evaluar_inversion, and no stated prerequisites or exclusions. The 'estimación ilustrativa, no una oferta de crédito' line clarifies the nature of the result but not when to select this tool.

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