Cambio Uruguay

Tasar un alquiler

estimate_fair_rent

Read-onlyIdempotent

Estima el alquiler justo de una vivienda concreta con avisos comparables de anunciantes distintos y, si se da askingPrice, ubica ese precio (percentil y % sobre o bajo la mediana). Para '¿me están cobrando caro?' o para negociar.

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": {
      "department": "<department>",
      "neighborhood": "<neighborhood>",
      "type": "<type>",
      "bedrooms": "<bedrooms>",
      "bathrooms": "<bathrooms>",
      "areaM2": "<areaM2>"
    },
    "name": "estimate_fair_rent"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	apartamento o casa.
`areaM2`	Yes	Superficie en m² (casas: construida).
`bedrooms`	Yes	Dormitorios (0 = monoambiente).
`currency`	No	Moneda de la estimación y de askingPrice (default UYU).
`areaBasis`	No	built = construida (default), total = con balcones y terrazas.
`bathrooms`	Yes	Baños.
`department`	Yes	Departamento con tildes: "Paysandú".
`askingPrice`	No	Alquiler pedido a evaluar, en currency.
`neighborhood`	Yes	Barrio como en los avisos, p. ej. "Pocitos".
`parkingSpaces`	No	Lugares de garaje.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / department / description

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

Changed10 schema fields changedOct 28, 2026

changedInput schema / properties / areaBasis / description

Previous value: -"built = construida (default), total = con balcones/terrazas."New value: +"built = construida (default), total = con balcones y terrazas."

changedInput schema / properties / areaM2 / description

Previous value: -"Superficie en m²."New value: +"Superficie en m² (casas: construida)."

changedInput schema / properties / askingPrice / description

Previous value: -"Precio pedido a evaluar, en la moneda indicada."New value: +"Alquiler pedido a evaluar, en currency."

addedInput schema / properties / bathrooms / description
```
Added value: +"Baños."
```
addedInput schema / properties / bedrooms / description
```
Added value: +"Dormitorios (0 = monoambiente)."
```

addedInput schema / properties / currency / description

Added value: +"Moneda de la estimación y de askingPrice (default UYU)."

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 / neighborhood / description

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

addedInput schema / properties / parkingSpaces / description
```
Added value: +"Lugares de garaje."
```
addedInput schema / properties / type / description
```
Added value: +"apartamento o casa."
```

AddedSep 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so safety is covered. The description adds genuine behavioral context beyond that: estimates are built from comparable listings from different advertisers, and askingPrice triggers additional outputs (percentile and % vs. median). It does not mention data-coverage limits or confidence, which would matter for a valuation tool.

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 sentences, both load-bearing: the first covers what is computed and the conditional behavior, the second covers the use case. The first sentence is dense and compound (two clauses joined by "y, si se da…"), which slightly hurts scannability but there is no filler.

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 10-parameter, no-output-schema tool, the description covers purpose, estimation method, the conditional return of percentile/deviation, and the intended question it answers. Remaining gaps (how sparse comparables are handled, currency default behavior) are partly covered by the schema, so nothing critical is missing for correct invocation.

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 description coverage is 100%, so the schema already defines all ten parameters (including defaults for currency and areaBasis). The description adds meaning only for askingPrice, explaining that supplying it changes the output to a percentile and deviation from median — extra semantics the schema does not convey.

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 and resource ("Estima el alquiler justo de una vivienda concreta") and adds the method — comparables from distinct advertisers — plus the conditional askingPrice evaluation. That scope implicitly separates it from aggregate siblings like rental_market_stats or compare_neighborhoods, but no sibling is named, so an agent must still infer the boundary.

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 closing sentence gives a concrete use context ("¿me están cobrando caro?" / negociar), which tells the agent when this tool fits. It offers no explicit exclusions or named alternatives for market-wide or listing-search questions, so routing decisions against siblings remain implicit.

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.