Skip to main content
Glama

Screen Spanish Real-Estate Auctions (Spain Node Only)

find_distressed_auctions
Read-onlyIdempotent

Search and rank Spanish judicial real-estate auctions from Catastro/BOE by region, maximum LTV, minimum value, and insolvency status; requires a DATAX token.

Instructions

Compatibility bridge for Spanish Catastro/BOE judicial real-estate auctions ($0.10 USDC or EURC via DATAX_TOKEN; returns HTTP 402 if unset). Unless DATAX_BASE_URL points to the Spain node (datax-spain-eu-mcp), calls on this Portugal server always return empty matches because Spanish property auctions are not indexed locally—prefer search_tenders or find_funded_companies for Portugal records.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_distressed_auctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of ranked auctions to return (1 to 25, default 10).
ambitoNoCase-insensitive province or region substring filter (e.g. 'Madrid' or 'Valencia'). Leave empty to search all regions.
max_ltv_pctNoMaximum claimed debt as a percentage of appraisal value (1 to 1000, default 100). Lower percentages indicate deeper discounts.
min_value_eurNoMinimum official appraisal or auction value in EUR (>= 0, default 0).
concursal_onlyNoWhen true, restrict results to bankruptcy/insolvency court auctions (SUB-JC-*).

Output Schema

NameRequiredDescriptionDefault
resultNo
statusNo
change_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv0.1.1
    • addedInput schema / properties / ambito / description
      Added value: +"Case-insensitive province or region substring filter (e.g. 'Madrid' or 'Valencia'). Leave empty to search all regions."
    • addedInput schema / properties / concursal_only / default
      Added value: +false
    • addedInput schema / properties / concursal_only / description
      Added value: +"When true, restrict results to bankruptcy/insolvency court auctions (SUB-JC-*)."
    • addedInput schema / properties / limit / default
      Added value: +10
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of ranked auctions to return (1 to 25, default 10)."
    • addedInput schema / properties / limit / maximum
      Added value: +25
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / max_ltv_pct / default
      Added value: +100
    • addedInput schema / properties / max_ltv_pct / description
      Added value: +"Maximum claimed debt as a percentage of appraisal value (1 to 1000, default 100). Lower percentages indicate deeper discounts."
    • addedInput schema / properties / max_ltv_pct / maximum
      Added value: +1000
    • addedInput schema / properties / max_ltv_pct / minimum
      Added value: +1
    • addedInput schema / properties / min_value_eur / default
      Added value: +0
    • addedInput schema / properties / min_value_eur / description
      Added value: +"Minimum official appraisal or auction value in EUR (>= 0, default 0)."
    • addedInput schema / properties / min_value_eur / minimum
      Added value: +0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "change_token": {
      +      "type": "string"
      +    },
      +    "result": {
      +      "properties": {
      +        "data_version": {
      +          "type": "string"
      +        },
      +        "matches": {
      +          "items": {
      +            "properties": {
      +              "ambito": {
      +                "description": "Geographic jurisdiction or region.",
      +                "type": "string"
      +              },
      +              "detail_locked": {
      +                "description": "Always true until unlocked with get_tender_detail.",
      +                "type": "boolean"
      +              },
      +              "fecha_pub": {
      +                "description": "Publication date in YYYYMMDD format.",
      +                "type": "string"
      +              },
      +              "importe_texto": {
      +                "description": "Formatted amount string when available.",
      +                "type": "string"
      +              },
      +              "item_ref": {
      +                "description": "Opaque encrypted record reference ('dx_...') for get_tender_detail.",
      +                "type": "string"
      +              },
      +              "notice_type": {
      +                "description": "Notice classification.",
      +                "type": "string"
      +              },
      +              "preview": {
      +                "description": "Redacted summary preview without PII or entity identifiers.",
      +                "type": "string"
      +              },
      +              "seccion": {
      +                "description": "Registry section code.",
      +                "type": "string"
      +              },
      +              "unlock_price_micros": {
      +                "description": "Unlock price in USD/EUR micros (500000 = 0.50).",
      +                "type": "integer"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "operation": {
      +          "type": "string"
      +        },
      +        "total_returned": {
      +          "type": "integer"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "status": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds value annotations cannot: paid access ($0.10 USDC or EURC via DATAX_TOKEN), an HTTP 402 failure mode when the token is unset, and the silent empty-result behavior on the Portugal node. Only the return payload shape is left unaddressed, which the output schema covers.

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?

Two dense sentences, front-loaded with the resource and the payment requirement, then the routing caveat. Every clause earns its place, though the first sentence packs payment, token name, and HTTP status into one long construct that is slightly hard to parse.

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 rich annotations, a full output schema, and fully documented parameters, the description supplies exactly the missing pieces: billing, credential requirement, failure behavior, and node routing. An agent has everything needed to decide whether to call it and what to expect.

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%, so all five parameters (limit, ambito, max_ltv_pct, min_value_eur, concursal_only) are already documented with ranges and meanings. The description adds no parameter-level detail, so the baseline of 3 applies.

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 the concrete resource — Spanish Catastro/BOE judicial real-estate auctions — with a specific scope and verb (screen/find). It also names the sibling tools (search_tenders, find_funded_companies) that serve Portugal records, so an agent can distinguish it from them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the condition under which this tool is useless (DATAX_BASE_URL not pointing at datax-spain-eu-mcp) and gives a direct routing instruction to the alternatives for Portugal data. Both when-to-use and when-not-to-use are covered.

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