Subastech — subastas judiciales de inmuebles (BOE)

Informe de viabilidad

informe

Read-onlyIdempotent

Informe de viabilidad de una subasta con las secciones que tu plan permite (resumen, cargas, descripción, catastro, calculadora, valoración, intervinientes, estadísticas); las cerradas se listan en locked. Requiere cuenta verificada (scope informes:read). Los tiers basic/completo solo se sirven si ya están desbloqueados: si no, devuelve unlock_required con la URL para desbloquearlos en el navegador (y, si el comercio para agentes está activo, compra.paymentLink para pagarlos por MPP). Nunca consume cuota ni cobra por sí misma. Parte del texto se genera con IA (disclosure).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Identificador público de la subasta (10 caracteres)
`tier`	No	`web` (por defecto, según tu plan), `basic` o `completo` (solo si ya están desbloqueados)

Output Schema

TableJSON Schema

Name	Required	Description
`ai`	No
`cta`	No
`tier`	Yes
`compra`	No
`locked`	Yes
`pdfUrl`	No
`subasta`	Yes
`secciones`	Yes
`disclosure`	No
`unlock_url`	No
`informe_url`	Yes
`analisis_listo`	Yes	false si polSaaS aún está generando el veredicto

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds substantial behavioral detail beyond that: it never consumes quota or charges by itself, locked sections are listed in `locked`, unavailable tiers return `unlock_required`, and part of the text is AI-generated via `disclosure`. No contradiction with annotations.

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?

The description is dense but every clause earns its place: purpose, sections, auth requirement, tier gating, lock behavior, payment possibility, quota neutrality, and AI disclosure. It is front-loaded with the core purpose and avoids filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and annotations cover safety, the description is complete enough for correct invocation. It covers prerequisites, account verification, scope, tier unlock conditions, fallback responses, quota/charging semantics, and AI disclosure. An agent has what it needs to select and call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 adds meaningful tier behavior: `basic`/`completo` only work when unlocked, otherwise `unlock_required` is returned, and it enriches the `tier` parameter meaning beyond the schema. It does not need to repeat the `id` format since the schema already documents it.

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?

The description clearly identifies the produced artifact: a viability report for an auction, with the exact sections included. Although phrased as a noun phrase, the meaning is unmistakable, and the `locked` distinction plus section list separates it from sibling auction tools like `subasta` or `analisis_subasta`.

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?

The description gives concrete usage context: it requires a verified account and scope `informes:read`, and it explains how locked tiers behave, including the `unlock_required` fallback and optional payment link. It does not explicitly name sibling alternatives or state when to prefer this tool over them, but the conditions for use are clear.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation3/5

Most tools are grouped into recognizable clusters (alertas, checkout, favoritos, notas), but several retrieval/report tools overlap: `fetch` and `subasta` both expose an auction record, and `analisis_subasta` and `informe` both provide analysis. The descriptions give enough distinguishing detail, but an agent must read closely to avoid misselection.

Naming Consistency2/5

Naming mixes Spanish and English, and mixes conventions: `alertas_crear` and `buscar_subastas` are Spanish compound names, `create_checkout`/`cancel_checkout` are English verb_noun, while `fetch`, `search`, `subasta` and `informe` are bare words. There is internal consistency within clusters, but no coherent pattern across the full toolset.

Tool Count2/5

32 tools is a large, heavy surface for one MCP server, exceeding the 25+ threshold where consolidation is usually needed. Many tools earn their place given the broad platform, but the multiple search/retrieval variants and five checkout lifecycle tools could be streamlined.

Completeness4/5

The server covers the core domain thoroughly: auction search/retrieval, viability reports, alerts, favorites, registry notes, market statistics, plans/account, and UCP checkout all have lifecycle coverage. Minor gaps exist, such as no explicit report-purchase history and some payment steps being delegated to a browser, but agents can complete most workflows.

Resources

Need Help?