Skip to main content
Glama

Screen Spanish Real-Estate Auctions (Spain Node Only)

find_distressed_auctions
Read-onlyIdempotent

Search Spanish Catastro/BOE judicial real-estate auctions by province, discount, value, and insolvency status; use the Spain node for results, as France records return empty matches.

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 France server always return empty matches because Spanish property auctions are not indexed locally—prefer search_tenders or find_funded_companies for France 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.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses a paid-call requirement ($0.10 USDC or EURC via DATAX_TOKEN) and the concrete failure mode of an HTTP 402 when the token is unset. It also warns that results will silently be empty in the default configuration, which is exactly the kind of non-obvious behavior an agent would otherwise misread as 'no auctions exist'.

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 sentences plus a parenthetical cover purpose, cost, auth failure, and alternatives with little waste. The parenthetical payment clause is jammed mid-sentence, slightly interrupting the front-loaded purpose statement, but overall it is tight and readable.

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

Completeness4/5

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

With an output schema present, the description needn't explain return values, and it covers the two things that would otherwise trip an agent: billing/auth and the empty-result trap on the wrong node. Complete enough to call correctly, with only the ranking semantics left entirely to the schema.

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 each of the five parameters (limit, ambito, max_ltv_pct, min_value_eur, concursal_only) carries a detailed inline description including ranges and defaults. The description adds no interpretation of its own, so the baseline of 3 applies.

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?

The description states the specific resource (Spanish Catastro/BOE judicial real-estate auctions) and frames it as a compatibility bridge, which is enough to distinguish it from search_tenders and find_funded_companies. The actual action (ranked auction screening) is only implied by the title rather than stated outright in the body, so it falls just short of a clean verb+resource statement.

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?

It explicitly names the conditions that matter: calls on this France server return empty matches unless DATAX_BASE_URL points at the Spain node, and it redirects the agent to search_tenders or find_funded_companies for France records. That is clear routing guidance, though it is framed entirely as a negative and never states the positive case (when the Spain node is active) in actionable terms.

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