Nido Raíz — Inmuebles en Colombia

Evaluar un inmueble como inversión

evaluar_inversion

Read-onlyIdempotent

Estima rentabilidad bruta, cap rate, flujo de caja apalancado y valorización de un inmueble en Colombia. Si no se indica el canon, lo estima con el rendimiento típico de la zona y lo dice. Es una estimación ilustrativa.

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": "evaluar_inversion"
  }
}

Input Schema

Name	Required	Description
`anios`	No	Horizonte de la inversión en años
`precio`	Yes	Precio del inmueble en pesos colombianos
`canonMensual`	No	Canon de arriendo mensual en pesos, si se conoce
`cuotaInicialPct`	No	Porcentaje de cuota inicial para el escenario apalancado

Output Schema

Name	Required	Description	Default
`estimacion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses two behaviors that matter: when canonMensual is omitted it imputes a value from typical zone yield and explicitly tells the user it did so, and the result is framed as an illustrative estimate rather than a valuation. This is real added context; it stops short of 5 only because nothing is said about the financial assumptions behind the leveraged cash-flow scenario.

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?

Three short sentences, each carrying distinct information: what is computed, how the missing canon is handled, and the accuracy caveat. No filler, and the key outputs are front-loaded.

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 an output schema exists, the description needn't explain return values, and it covers the highest-risk gap (silent imputation of missing inputs) plus an accuracy disclaimer. It is slightly incomplete on default behavior for cuotaInicialPct and the horizon, which shape the leveraged scenario an agent will report.

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 a 3 is the baseline, but the description adds genuine meaning about canonMensual's optional handling (auto-estimated from zone yield with disclosure), which is behavior the schema's 'si se conoce' does not convey. The other parameters (precio, anios, cuotaInicialPct) are left entirely to the schema, and any defaults for cuotaInicialPct are unmentioned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Estima') and enumerates the concrete outputs: rentabilidad bruta, cap rate, flujo de caja apalancado y valorización, plus the geographic scope (Colombia). It does not explicitly differentiate itself from the overlapping sibling calcular_financiacion, so it falls short of a 5.

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 framing 'evaluar un inmueble como inversión'; there is no explicit when-to-use statement, no mention of prerequisites, and no routing away from calcular_financiacion, which an agent could plausibly confuse with this tool.

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

All Nido Raíz — Inmuebles en Colombia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?