Subastech — subastas judiciales de inmuebles (BOE)

Buscar subastas

buscar_subastas

Read-onlyIdempotent

Busca subastas judiciales de inmuebles del BOE por provincia, municipio, tipo, precio, superficie, texto libre, zona (bbox o radio) y estado. Pública, sin cuenta: devuelve datos oficiales del BOE y la URL de cada ficha. El scoring, veredicto, cargas, ROI, valoración e intervinientes requieren cuenta y plan Pro o superior; si algo está cerrado se devuelve locked con upgradeUrl. Sin plan con scoring, orden: score pasa a recent y solo_viables se ignora (campo degradado). Máximo 20 por página (por_pagina, o su alias limite); no acepta parámetros que no estén declarados.

Input Schema

TableJSON Schema

Name	Required	Description
`bbox`	No	Zona rectangular en grados (lon/lat)
`tipo`	No	Tipos de inmueble, valores EXACTOS de `estadisticas_publicas.tipos` (p. ej. `Vivienda`, `Garaje`)
`cerca`	No	Radio alrededor de un punto (máximo 50 km)
`orden`	No	`recent` (por defecto), `ending`, `discount`, `price`; `score` solo con plan Pro (si no, pasa a `recent`)
`texto`	No	Texto libre (calle, barrio, juzgado…), máximo 120 caracteres
`estado`	No	`activas` (por defecto), `todas`, `adjudicadas` o `desiertas`
`limite`	No	Alias de `por_pagina` (número de resultados por página). Si indicas los dos, manda `por_pagina`.
`pagina`	No	Página (≥1; máximo 25 sin cuenta, 50 con cuenta)
`area_max`	No	Superficie construida máxima (m²)
`area_min`	No	Superficie construida mínima (m²)
`municipio`	No	Claves `provincia:municipio` (de `estadisticas_publicas` con `municipio_q`)
`provincia`	No	Slugs de provincia (p. ej. [`madrid`, `barcelona`]); ver `estadisticas_publicas`
`por_pagina`	No	Resultados por página (1..20)
`precio_max`	No	Valor de subasta máximo (euros)
`precio_min`	No	Valor de subasta mínimo (euros)
`solo_viables`	No	Ocultar las no recomendables: solo con plan Pro (si no, se ignora)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cta`	No
`items`	Yes
`total`	Yes
`locked`	No
`pagina`	Yes
`hasMore`	Yes
`paginas`	Yes
`degradado`	No
`disclosure`	No
`por_pagina`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 13, 2026

addedOutput schema / properties / items / items / properties / cadastralReview

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "id",
-  "type",
-  "isNew",
-  "title",
-  "address",
-  "municipio",
-  "provincia",
-  "cp",
-  "ref",
-  "provinceSlug",
-  "municipalitySlug",
-  "end",
-  "contentUpdatedAt",
-  "daysLeft",
-  "valueAuction",
-  "valueM2",
-  "minimumBid",
-  "deposit",
-  "appraisal",
-  "occupied",
-  "discount",
-  "m2",
-  "status",
-  "cadastral",
-  "imageUrl",
-  "lat",
-  "lon",
-  "lot",
-  "finalBid",
-  "resultStatus",
-  "closedAt",
-  "phase",
-  "url",
-  "links",
-  "fuente"
-]New value: +[
+  "id",
+  "type",
+  "isNew",
+  "title",
+  "address",
+  "municipio",
+  "provincia",
+  "cp",
+  "ref",
+  "provinceSlug",
+  "municipalitySlug",
+  "end",
+  "contentUpdatedAt",
+  "daysLeft",
+  "valueAuction",
+  "valueM2",
+  "minimumBid",
+  "deposit",
+  "appraisal",
+  "occupied",
+  "discount",
+  "m2",
+  "status",
+  "cadastral",
+  "cadastralReview",
+  "imageUrl",
+  "lat",
+  "lon",
+  "lot",
+  "finalBid",
+  "resultStatus",
+  "closedAt",
+  "phase",
+  "url",
+  "links",
+  "fuente"
+]

Changed1 schema field changedOct 2, 2026

changedOutput schema / properties / items / items / properties / phase / enum

Previous value: -[
-  "activa",
-  "historica",
-  "descartada"
-]New value: +[
+  "activa",
+  "historica",
+  "descartada",
+  "suspendida"
+]

Changed4 schema fields changedSep 11, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / bbox / additionalProperties
```
Added value: +false
```
addedInput schema / properties / cerca / additionalProperties
```
Added value: +false
```

addedInput schema / properties / limite

Added value: +{
+  "description": "Alias de `por_pagina` (número de resultados por página). Si indicas los dos, manda `por_pagina`.",
+  "maximum": 20,
+  "minimum": 1,
+  "type": "integer"
+}

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, non-destructive). The description adds substantial behavior beyond that: locked fields return `locked` with `upgradeUrl`, plan-gated ordering degrades with a `degradado` field, hard cap of 20 per page, alias precedence for `limite`/`por_pagina`, and rejection of undeclared parameters.

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?

Front-loads the capability and filter axes in the first sentence, then layers access model, plan gating and limits in short declarative sentences. Every clause carries actionable information with no filler or repetition.

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 16-parameter tool with nested objects, enums and an output schema, the description covers the decision-critical behavior (free vs Pro, locked/degraded responses, pagination limits). Remaining detail such as coordinate semantics and the provenance of provincia/municipio keys is left entirely to the schema, which is a minor but real gap.

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 schema already documents all 16 parameters, including enum values, bbox/cerca structure and slug patterns. The description reinforces the page-size cap and the `limite` alias precedence but adds no syntax or format detail beyond what the schema provides, so the baseline of 3 applies.

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 and resource ('Busca subastas judiciales de inmuebles del BOE') and enumerates the exact filter axes: provincia, municipio, tipo, precio, superficie, texto, zona, estado. An agent can distinguish this from siblings like `subasta`, `buscar_por_codigo` or `estadisticas_publicas` without opening any schema.

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?

Clearly states the access context: public and account-free, with scoring/ROI/intervinientes gated behind Pro, plus the exact degradation rules when the plan is missing (`orden: score` falls back to `recent`, `solo_viables` ignored). It does not name alternative tools for related tasks (detail lookup, analysis, statistics), so it stops short of explicit when-not guidance.

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

All Subastech — subastas judiciales de inmuebles (BOE) 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.

Resources

Need Help?