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): usa total, paginas y hasMore para pedir la siguiente.

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 readOnly/idempotent/non-destructive, so the bar is low. The description still adds real value beyond them: the required account and `alertas:read` scope, and the pagination contract (20 per page max, follow via `total`/`paginas`/`hasMore`).

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: purpose first, then the auth prerequisite, then the pagination mechanics. Every sentence carries information; 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?

With an output schema present, returns need not be described, and the description correctly focuses on the auth scope and pagination workflow. Slightly incomplete only in not surfacing the `limite` alias, but nothing essential for a correct call is missing.

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 coverage is 100%, so the baseline is 3. The description restates the `pagina`/`por_pagina` pagination and the 20-per-page cap, but omits the `limite` alias parameter documented in the schema, adding little beyond what the schema already conveys.

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 ('Lista') and resource ('tus alertas de subastas') and enumerates the returned facets (criterios, tipos de aviso, cadencia, canales, estado). Among the sibling alert tools (crear/editar/eliminar/activar/previsualizar), the read/list verb makes this unmistakably the retrieval operation.

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?

It supplies a prerequisite (requires an account with scope `alertas:read`), which is useful selection context. However, it never states when to prefer this over siblings like alertas_previsualizar nor any when-not-to-use condition, so usage is only implied.

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?