Skip to main content
Glama

Subastech — subastas judiciales de inmuebles (BOE)

Análisis de una subasta (veredicto y ejes)

analisis_subasta
Read-onlyIdempotent

Veredicto de viabilidad y ejes (cargas, posesión, rentabilidad, titularidad) de una subasta. Requiere cuenta (scope informes:read) y plan Pro o superior; con Radar/Starter devuelve locked con upgradeUrl. No consume cuota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesIdentificador público de la subasta (10 caracteres)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctaNo
ejesNo
lockedNo
subastaYes
veredictoNo
disclosureNo
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.3/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description adds genuinely new behavior: required auth scope, plan-tier gating with a `locked` fallback payload, and the notable fact that it does not consume quota. Those are exactly the operational facts an agent cannot get from annotations or schema.

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?

Two dense sentences, front-loaded with what the tool returns before moving to access conditions. Every clause carries information — scope, tier, fallback, quota — with no 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?

For a single-parameter read tool with an output schema and full annotation coverage, the description supplies everything else an agent needs: access requirements, tier-gating behavior, the shape of the gated response, and the cost model. Nothing material 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 single `id` parameter is documented in the schema with its 10-character pattern, so the baseline is 3. The description adds no further parameter detail, which is acceptable here since there is nothing left to clarify.

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 (viability verdict plus axes for an auction) and enumerates the four axes returned, which is far more informative than the title alone. It never names the adjacent siblings (subasta, informe, recomendaciones), so an agent must infer which one to pick, keeping this at a 4.

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 clear preconditions: account required, `informes:read` scope, Pro plan or higher, and explicitly what happens on lower tiers (returns `locked` with `upgradeUrl`). That is effectively a when-not condition, but it never contrasts the tool with the similarly-named `informe` or `subasta` siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources