Skip to main content
Glama

Buscar viviendas

buscar_viviendas
Read-onlyIdempotent

Busca subastas de viviendas abiertas y pisos de banco en venta en una provincia española, con filtros de municipio, precio, superficie, habitaciones, descuento sobre la tasación, días hasta el cierre, ocupación y cargas. Devuelve hasta 50 resultados con la URL de la ficha de cada uno.

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": {
      "provincia": "<provincia>"
    },
    "name": "buscar_viviendas"
  }
}

Input Schema

NameRequiredDescriptionDefault
tipoNoSolo subastas, solo pisos de banco o los dos.todas
ordenNoprecio ascendente, descuento descendente, cierre más próximo o €/m² ascendente.precio
limiteNo
m2_minNoSuperficie mínima, en m².
municipioNoMunicipio, tal como se escribe (Elche, Torrevieja…).
provinciaYesNombre de la provincia (Alicante, Valencia, Madrid…).
precio_maxNoPrecio o valor de subasta máximo, en euros.
precio_minNoPrecio o valor de subasta mínimo, en euros.
sin_cargasNoSolo subastas cuyo expediente dice expresamente que no hay cargas.
solo_libresNoSolo subastas cuyo expediente dice que la vivienda está libre de ocupantes.
descuento_minNoSolo subastas: descuento mínimo sobre la tasación, en %.
cierra_en_diasNoSolo subastas: que cierren dentro de estos días.
habitaciones_minNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds real behavior beyond that: a hard cap of 50 returned results, the inclusion of a per-listing ficha URL, and the fact that descuento, cierre, ocupación and cargas filters apply only to subastas — important because an agent filtering pisos de banco would otherwise expect them to apply. It does not mention pagination or what happens when more than 50 match.

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 sentences, front-loaded with what is searched and where, followed by the filter axes and the return contract. No filler, no repetition of the title.

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 13-parameter search tool with no output schema, the description covers the essentials: scope, filter families, result cap and the URL returned per record. Missing only secondary details such as default result count behavior when limite is omitted and how results are ordered when orden is not set.

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 85%, so the schema already explains nearly every parameter, including the enum meanings for tipo and orden. The description only echoes the filter list and restates the 50-result ceiling, adding little semantic detail (e.g. whether precio applies to bank listings as well as auction values, or how descuento is computed) 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?

Names a specific verb (buscar) and precise resources (subastas de viviendas abiertas y pisos de banco en venta) scoped to a Spanish province, plus the filter axes and the return shape. It is clearly not ficha_vivienda (detail lookup) or listar_provincias, but it never explicitly distinguishes itself from subastas_que_cierran or resumen_mercado, which overlap with its cierra_en_dias and market-scope angles.

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: use it to find candidate listings in a province with filters. There is no explicit when-to-use versus the siblings, no statement that subastas_que_cierran is the shortcut for closing-soon searches, and no prerequisites (e.g. that provincia must be a valid name obtainable via listar_provincias).

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