Skip to main content
Glama

DealScreener: Spanish property auctions

Buscar subastas e inmuebles cribados

search_auctions
Read-onlyIdempotent

Busca subastas de inmuebles en España (BOE y otras) e inmuebles de bancos ya cribados, con su veredicto (INTERESANTE, VIGILAR, DESCARTAR) y puntuación de 0 a 100. Filtra por provincia, municipio, tipo de activo, puntuación mínima, veredicto y semana de cierre. Los importes y superficies se dan como rangos. Como máximo 25 resultados, cada uno con el enlace a su ficha en dealscreener.io. Solo cribado, no asesoramiento.

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

Input Schema

NameRequiredDescriptionDefault
tipoNoTipo de activo.
limiteNoNúmero de resultados (1-25, por defecto 10).
origenNoSubastas (por defecto), inmuebles de bancos, anuncios de portales o todos.
municipioNoMunicipio, p. ej. "Getafe".
provinciaNoProvincia, p. ej. "Madrid", "Valencia", "Málaga".
score_minNoPuntuación mínima (0-100).
veredictoNoSolo este veredicto.
cierra_antes_deNoSolo subastas cuya semana de cierre empieza en o antes de esta fecha (AAAA-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: a hard cap of 25 results, amounts and surface areas returned as ranges rather than exact figures, and the scope disclaimer "Solo cribado, no asesoramiento" — all useful for interpreting the response.

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?

Four sentences, front-loaded with what is searched and what comes back, then filters, then result-shape constraints, then the disclaimer. No sentence is padding; each carries either scope, filtering capability, output shape, or a usage caveat.

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?

With eight optional parameters, no output schema and annotations already covering safety, the description carries the right load: it explains result count, range-based values, verdict/score fields and the per-item link. The only gap is pagination or what to do when the 25-result ceiling truncates a search, which an agent must 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 description coverage is 100%, so every parameter is already documented, which sets the baseline at 3. The description restates the filter dimensions and clarifies that closing dates are handled by week, but adds little syntax or defaulting detail beyond what the schema and enums already provide (e.g., origen default and limite default live in the schema).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Busca") plus the exact resource and scope: property auctions in Spain (BOE and others) and pre-screened bank-owned properties. It also names the output artifacts (veredicto INTERESANTE/VIGILAR/DESCARTAR, score 0-100) and the link to each ficha, which implicitly separates it from a single-item detail tool like get_deal.

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?

The description enumerates the filter dimensions (provincia, municipio, tipo de activo, puntuación mínima, veredicto, semana de cierre), which implies when the tool is useful for narrowing a search. However, it never states when NOT to use it or names the sibling get_deal as the alternative for retrieving a single property's full record; the routing is 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