Skip to main content
Glama
Sign In

Cambio Uruguay

by io.github.eduair94
OverviewDiscussionsAdmin

Comparar barrios

compare_neighborhoods
Read-onlyIdempotent

Compara barrios con datos públicos: alquiler mediano y total, precio por m², delitos denunciados (Ministerio del Interior), cortes de agua (OSE), reclamos a la IM, servicios cercanos y el puesto de cada barrio entre los 62 de Montevideo. Pasá neighborhoods para comparar esos, o rankBy para listar los mejores.

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

Input Schema

NameRequiredDescriptionDefault
typeNoPrecios de apartamentos (default) o casas.
limitNoBarrios a devolver al rankear (default 10).
rankByNorent = más baratos (default), monthly = menor total, safety = menos denuncias, services = más servicios.
bedroomsNoDormitorios de los precios (default any).
departmentNoDepartamento con tildes: "Paysandú".
neighborhoodsNoBarrios a comparar, p. ej. ["Pocitos", "Malvín"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / department / description
      Previous value: -"Departamento con tildes, p. ej. \"Montevideo\", \"Maldonado\"."New value: +"Departamento con tildes: \"Paysandú\"."
  2. Changed5 schema fields changed
    • addedInput schema / properties / bedrooms / description
      Added value: +"Dormitorios de los precios (default any)."
    • 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 / limit / description
      Added value: +"Barrios a devolver al rankear (default 10)."
    • addedInput schema / properties / neighborhoods / description
      Added value: +"Barrios a comparar, p. ej. [\"Pocitos\", \"Malvín\"]."
    • addedInput schema / properties / rankBy / description
      Added value: +"rent = más baratos (default), monthly = menor total, safety = menos denuncias, services = más servicios."
  3. Added

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, so the bar is lower. The description adds real behavioral context: the data provenance (Ministerio del Interior, OSE, IM) and the scope of the ranking universe (62 barrios de Montevideo), which tells the agent the comparison set is bounded and official-sourced.

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 payload of metrics comes first, then the how-to-use clause. Zero filler and nothing repeated from the schema.

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?

There is no output schema, so the description carries the return-value burden — and it does so well by listing every metric and the ranking position. Minor gap: it doesn't say what happens when a neighborhood has no data, or how a cross-department query behaves despite the department parameter.

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%, so the baseline is 3. The description reinforces the neighborhoods-vs-rankBy split and the ranking mode, but adds no syntax or edge-case detail beyond what the schema already documents (e.g. that department widening the search exists but conflicts with the '62 barrios de Montevideo' framing).

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 (comparar) and resource (barrios), and enumerates the exact metrics returned: alquiler mediano y total, precio por m², delitos, cortes de agua, reclamos, servicios, ranking entre 62 barrios. An agent immediately knows what it gets, though it never names a sibling tool to distinguish itself from rental_market_stats or find_property_opportunities.

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?

"Pasá neighborhoods para comparar esos, o rankBy para listar los mejores" gives explicit mode-selection guidance between the two behaviors. What's missing is cross-tool guidance: nothing says when to use this instead of rental_market_stats or rank_rentals_for_household.

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

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