Skip to main content
Glama

Nido Raíz — Inmuebles en Colombia

Buscar inmuebles en Colombia

buscar_inmuebles
Read-onlyIdempotent

Busca vivienda en venta o arriendo publicada por inmobiliarias colombianas: apartamentos, casas, fincas, lotes y locales. Los límites de precio son en COP y excluyen otras monedas o moneda desconocida, sin convertir divisas. Con negocio rent limita el canon mensual; sin negocio compara el campo de precio y no restringe la operación. Devuelve el total real de coincidencias y la URL de cada ficha.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buscar_inmuebles"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoTexto libre cuando no se sabe si es ciudad, barrio o dirección
tipoNoTipo de inmueble. lot es lote urbano, land es terreno rural, local es local comercial
banosNoNúmero mínimo de baños que debe tener el inmueble
barrioNoBarrio o sector
cursorNoPara la página siguiente: el "cursorSiguiente" de la respuesta anterior, sin cambiar los demás filtros
limiteNoResultados por página. Por defecto 8, máximo 20
alcobasNoAlcobas mínimas
areaMinNoÁrea construida mínima en m²
estratoNoEstrato socioeconómico colombiano, de 1 a 6. Indica el nivel del sector y determina el costo de los servicios públicos
negocioNosale = venta, rent = arriendo; cada opción incluye los inmuebles ofrecidos en ambas modalidades (sale_rent)
municipioNoMunicipio o ciudad. Ej: "Medellín", "Envigado", "Bogotá", "Sabaneta"
precioMaxNoLímite positivo en COP. Con negocio rent es el canon mensual; con sale o sin negocio es el campo de precio. 400 millones se escribe 400000000
precioMinNoLímite positivo en COP. Con negocio rent es el canon mensual; con sale o sin negocio es el campo de precio. 400 millones se escribe 400000000

Output Schema

NameRequiredDescriptionDefault
notaNo
devueltosYes
resultadosYes
cursorSiguienteYes
totalCoincidenciasYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent, and the description adds real behavioral detail beyond them: prices are never converted between currencies and listings in other or unknown currencies are dropped, and 'sin negocio' compares the price field without restricting operation type. It also discloses that the response reports the true total match count plus a URL per listing.

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 dense sentences, front-loaded with the what and where, followed by the currency and negocio rules and then the return shape. No filler, though the closing sentence on return values is partly redundant given an output schema exists.

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?

A 13-parameter, zero-required search tool with a full output schema; the description covers purpose, geographic scope, currency semantics, negocio branching, and return summary. Pagination is delegated to the schema's cursor description, which is reasonable, leaving little an agent would need to guess.

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 coverage is 100%, so the baseline is 3; the schema already documents precioMin/precioMax, negocio, limite and cursor in comparable detail. The description adds the non-conversion rule and the fallback behavior when negocio is omitted, but beyond those points it largely restates what the schema already says.

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?

Opens with a concrete verb plus resource ('Busca vivienda en venta o arriendo') and enumerates the property types covered (apartamentos, casas, fincas, lotes, locales), scoped to Colombian listings. An agent can distinguish this search tool from a detail tool like ver_inmueble, though no sibling is explicitly named.

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?

Provides conditional context for price filtering via 'negocio' (rent vs sale) and excludes non-COP listings, which implicitly tells the agent when the price filters are meaningful. However, it never states when to prefer this tool over ver_inmueble, listar_proyectos or evaluar_inversion, so alternatives are left to inference.

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