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.

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

Input 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

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.

Changed2 schema fields changedOct 25, 2026
- removedOutput schema / properties / alertas / items / properties / ultima_notificacion / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / alertas / items / properties / ultima_notificacion / type
```
Added value: +[
+  "string",
+  "null"
+]
```

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.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the description's added value is the auth scope requirement and the paging envelope (max 20 per page, response contains total/paginas/hasMore). That is real operational context beyond the structured fields; only rate-limit/ordering behavior is absent.

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?

Three short sentences, front-loaded with the resource and payload, then auth, then paging. 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?

An output schema exists, so explaining return fields is optional; mentioning total/paginas/hasMore is mildly redundant but harmless. The only meaningful gap is no note on default ordering or that empty results are a normal outcome for an account with no alerts.

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 restates the `pagina`/`por_pagina` cap of 20 but omits the `limite` alias and its precedence rule, so it adds little beyond the schema and even leaves out one documented nuance.

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') plus the fields returned (criterios, tipos de aviso, cadencia, canales, estado), which cleanly separates it from the mutating siblings alertas_crear/editar/eliminar. It does not explicitly name a sibling alternative, so it lands just short of a 5.

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?

Gives an important precondition ('Requiere cuenta (scope `alertas:read`)') and pagination constraints, but never says when to prefer this over e.g. favoritos_listar or alertas_previsualizar, nor any when-not condition. Usage is implied by the read-only listing verb rather than stated.

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?