Cambio Uruguay

Oportunidades inmobiliarias

find_property_opportunities

Read-onlyIdempotent

Viviendas pedidas por DEBAJO de avisos comparables (mismo barrio, tipo, dormitorios y superficie, varios anunciantes), con la brecha %, una brecha conservadora, cuántos comparables la sostienen y las cautelas. Alquiler compara alquiler + gastos comunes. Compara precios pedidos, no es una tasación.

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

Input Schema

Name	Required	Description
`page`	No	Página, desde 1.
`sort`	No	evidence = más sólidas primero, discount = mayor brecha.
`type`	No	Default: los dos.
`signal`	No	Brecha por precio total o por precio del m².
`perPage`	No	Resultados por página (default 8).
`bedrooms`	No	Dormitorios exactos.
`evidence`	No	standard = comparación sustentada, exploratory = para explorar.
`maxPrice`	No	Tope: pesos por mes (alquiler + gastos comunes) en alquiler, dólares en venta.
`operation`	No	rent = alquiler (default), sale = venta.
`confidence`	No	supported = más sólida, limited = con limitaciones.
`department`	No	Departamento con tildes: "Paysandú".
`neighborhood`	No	Barrio como en los avisos, p. ej. "Pocitos".

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

changedInput schema / properties / department / description

Previous value: -"Departamento con tildes, p. ej. \"Montevideo\", \"Maldonado\"."New value: +"Departamento con tildes: \"Paysandú\"."

changedInput schema / properties / page / description

Previous value: -"Página de resultados, desde 1."New value: +"Página, desde 1."

Changed10 schema fields changedOct 28, 2026

addedInput schema / properties / confidence / description

Added value: +"supported = más sólida, limited = con limitaciones."

changedInput schema / properties / department / description

Previous value: -"Departamento de Uruguay con tildes, p. ej. \"Montevideo\", \"Canelones\", \"Maldonado\", \"Colonia\"."New value: +"Departamento con tildes, p. ej. \"Montevideo\", \"Maldonado\"."

addedInput schema / properties / evidence / description

Added value: +"standard = comparación sustentada, exploratory = para explorar."

changedInput schema / properties / maxPrice / description

Previous value: -"Tope del precio comparado: pesos por mes en alquiler (alquiler + gastos comunes), dólares en venta."New value: +"Tope: pesos por mes (alquiler + gastos comunes) en alquiler, dólares en venta."

addedInput schema / properties / neighborhood / description

Added value: +"Barrio como en los avisos, p. ej. \"Pocitos\"."

addedInput schema / properties / page / description
```
Added value: +"Página de resultados, desde 1."
```

addedInput schema / properties / perPage / description

Added value: +"Resultados por página (default 8)."

addedInput schema / properties / signal / description

Added value: +"Brecha por precio total o por precio del m²."

addedInput schema / properties / sort / description

Added value: +"evidence = más sólidas primero, discount = mayor brecha."

addedInput schema / properties / type / description
```
Added value: +"Default: los dos."
```

AddedSep 21, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real methodological context: comparables must share barrio, type, bedrooms and surface across multiple advertisers, the output includes caveats ('cautelas'), and it explicitly disclaims being an appraisal. It doesn't discuss pagination or result ordering limits, keeping it below a 5.

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?

Two dense sentences, front-loaded with the core behavior and the gap metrics, then a caveat sentence. No filler, though the parenthetical example list is somewhat compressed.

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 12-parameter, no-output-schema tool, the description does explain what comes back (gap %, conservative gap, comparable count, caveats) and the rent vs sale comparison basis. Remaining gaps are minor: ordering, pagination behavior, and no explicit routing to alternative tools.

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 schema already documents all 12 parameters and enums. The description adds some meaning by implying the filters (barrio, tipo, dormitorios, superficie) define the comparable set, and clarifies that rent comparisons include gastos comunes, but it does not explain sort, evidence, confidence or signal beyond the schema.

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+resource: finds properties asking below comparable listings, with gap %, conservative gap, comparable count and caveats. It implicitly separates itself from a valuation tool ('no es una tasación') but does not name a sibling like estimate_fair_rent directly, so it stops short of full sibling-level differentiation.

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 implied: it's for spotting underpriced listings versus comparables, and the rent/sale comparison basis is noted. However, it never says when to prefer this over estimate_fair_rent, list_houses or search_rentals, nor any exclusions or prerequisites for the comparison.

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

All Cambio Uruguay 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.