Skip to main content
Glama

Subastech — subastas judiciales de inmuebles (BOE)

by com.subastech
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
idYesIdentificador público de la subasta (10 caracteres)
tierNo`web` (por defecto, según tu plan), `basic` o `completo` (solo si ya están desbloqueados)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
aiNo
ctaNo
tierYes
compraNo
lockedYes
pdfUrlNo
subastaYes
seccionesYes
disclosureNo
unlock_urlNo
informe_urlYes
analisis_listoYesfalse si polSaaS aún está generando el veredicto

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / subasta / properties / axes / anyOf
      Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "cargas": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "posesion": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "rentab": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "titularidad": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "cargas",
-      "posesion",
-      "rentab",
-      "titularidad"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "cargas": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "cargasMotivo": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "posesion": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "rentab": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "titularidad": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "cargas",
+      "posesion",
+      "rentab",
+      "titularidad"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedOutput schema / properties / subasta / properties / cadastralReview
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / subasta / 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"
+]
  2. Changed1 schema field changed
    • changedOutput schema / properties / subasta / properties / phase / enum
      Previous value: -[
-  "activa",
-  "historica",
-  "descartada"
-]New value: +[
+  "activa",
+  "historica",
+  "descartada",
+  "suspendida"
+]
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations (which already declare it read-only and idempotent): it never consumes quota or charges, requires a specific OAuth scope, returns `unlock_required` with an unlock URL plus an optional `compra.paymentLink`, and discloses that part of the output is AI-generated. That is exactly the extra context an agent needs to handle failures gracefully.

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?

Front-loads the purpose and packs auth, tier, quota, and disclosure facts into one dense but readable paragraph with no filler sentences. Slightly long, but every clause earns its place.

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 a rich output schema (so return shapes need no explanation) and full annotation coverage, the description still supplies auth scope, tier gating, the unlock fallback, quota/cost guarantees, and AI-content disclosure. Nothing an agent needs to invoke it correctly 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 description coverage is 100% and the enum already documents `web`/`basic`/`completo` and the unlocked-only condition, so the description largely repeats the schema. It adds only the behavioral consequence (the `unlock_required` fallback), which is not strictly parameter meaning, so baseline 3 fits.

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+resource: it produces a viability report (`informe de viabilidad`) for an auction and enumerates exactly which sections it can contain. It does not explicitly differentiate itself from close siblings such as `subasta` or `analisis_subasta`, so an agent must infer the boundary, but the purpose itself is unmistakable.

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 real preconditions: verified account with scope `informes:read`, and that `basic`/`completo` are only served if already unlocked, otherwise it returns `unlock_required`. It stops short of an explicit when-to-use-this-vs-siblings statement, but the situational context is 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) toolsInspect
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