Skip to main content
Glama

Subastech — subastas judiciales de inmuebles (BOE)

by com.subastech
OverviewDiscussionsAdmin

Recomendaciones para ti

recomendaciones
Read-onlyIdempotent

Subastas recomendadas según tu historial (tipo, precio, provincias), como el bloque «para ti» de la web. Requiere cuenta (scope cuenta:read). Con plan Pro o superior usa el ranking por scoring; si no, se construye con tu perfil y orden por fecha de fin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctaNo
notaNo
itemsYes
tituloNo
disclosureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / items / items / 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 / items / items / properties / cadastralReview
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / items / items / 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 / items / items / 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/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 safety profile is covered. The description adds real value beyond that: an auth requirement (scope `cuenta:read`) and the fact that output differs by plan (scoring-based for Pro+, profile + end-date ordering otherwise) — behavior an agent could not infer from structured fields.

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 tight sentences, front-loaded with what the tool returns, then the access requirement, then the behavioral nuance. Each sentence adds distinct information with no repetition or 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?

An output schema exists, so return shape need not be described, and annotations carry the safety profile. With auth scope and plan-dependent behavior documented, an agent has everything needed to decide to call it and predict the result set.

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?

The tool takes zero parameters and the schema is trivially complete, so there is nothing for the description to clarify. Baseline for a parameterless tool is 4.

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 ('Subastas recomendadas') and the personalization basis ('según tu historial'), with the fields it draws on (tipo, precio, provincias) and the web equivalent ('para ti'). Clear enough to distinguish from generic search, though it never names a sibling like 'similares' or 'buscar_subastas' to sharpen the boundary.

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 a prerequisite (account with scope `cuenta:read`) and explains the plan-dependent ranking, which implies when the tool is applicable. However, it never states when to prefer this over alternatives such as 'similares' or 'buscar_subastas', so selection guidance remains implied rather than explicit.

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