Subastech — subastas judiciales de inmuebles (BOE)

Listar mis alertas

alertas_listar

Read-onlyIdempotent

Lista tus alertas de subastas con sus criterios, tipos de aviso, cadencia, canales y estado. Requiere cuenta (scope alertas:read). Paginada (pagina, por_pagina; máximo 20 por página); la respuesta incluye total, paginas y hasMore.

Input Schema

TableJSON Schema

Name	Required	Description
`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; 1 por defecto)
`por_pagina`	No	Resultados por página (1..20; 20 por defecto)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cta`	No
`total`	Yes
`pagina`	Yes
`alertas`	Yes
`hasMore`	Yes
`paginas`	Yes
`disclosure`	No
`por_pagina`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 11, 2026

addedInput schema / 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"
+}

addedInput schema / properties / pagina

Added value: +{
+  "description": "Página (≥1; 1 por defecto)",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / por_pagina

Added value: +{
+  "description": "Resultados por página (1..20; 20 por defecto)",
+  "maximum": 20,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / hasMore
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / pagina
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / paginas
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / por_pagina
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / total
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / required

Previous value: -[
-  "alertas"
-]New value: +[
+  "alertas",
+  "pagina",
+  "por_pagina",
+  "total",
+  "paginas",
+  "hasMore"
+]

First observedSep 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false/openWorldHint=false, so safety is covered structurally. The description adds the auth scope requirement and the pagination contract (max 20 per page, response carries `total`, `paginas`, `hasMore`), which is genuine extra context beyond the annotations.

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?

Three tight sentences, front-loaded with the purpose, then prerequisites, then pagination. Every sentence carries information, though the pagination/response details partly duplicate what the schema and output schema already state.

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 read-only, zero-required-param listing tool with an output schema and rich annotations, the description covers purpose, auth scope and pagination adequately. It omits only edge behavior (empty results, ordering of alerts) and any routing advice toward sibling read tools.

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 `limite`, `pagina` and `por_pagina` are already fully documented, including the alias precedence rule. The description repeats the page-size cap and names two of the three params but adds no semantics beyond the schema, so the baseline 3 applies.

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 ('Lista') and resource ('tus alertas de subastas'), and enumerates the content returned (criterios, tipos de aviso, cadencia, canales, estado), which makes it unmistakable next to alertas_crear/editar/eliminar/activar/previsualizar. It does not explicitly name a sibling it could be confused with, so it stops short of the top band.

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?

Gives a clear precondition — 'Requiere cuenta (scope `alertas:read`)' — and the pagination context tells the agent this is a browsing call, not a lookup. However, it never states when to prefer it over the related read tools (favoritos_listar, notas_simples_listar) or when alertas_previsualizar would be the right call instead.

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?