Skip to main content
Glama

Screen Spanish Real-Estate Auctions (Spain Node Only)

find_distressed_auctions
Read-onlyIdempotent

Find distressed Spanish judicial real-estate auctions by province, value, LTV, and bankruptcy status; route to the Spain node with DATAX_TOKEN to get 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 Italy server always return empty matches because Spanish property auctions are not indexed locally—prefer search_tenders or find_funded_companies for Italy 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.3/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description goes well beyond them: per-call cost ($0.10 USDC or EURC), the DATAX_TOKEN credential requirement, the HTTP 402 response when the token is unset, and the silent-empty-result behavior when routed to the wrong node. These are exactly the operational traits an agent needs and none are recoverable from annotations.

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, no filler, and the critical routing caveat is front-loaded alongside the cost. Slightly dense — payment plumbing, node routing, and sibling alternatives are packed into one breath — but nothing is redundant.

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 annotations covering the safety profile and an output schema covering return shape, the description supplies the remaining essentials: cost, credential, routing prerequisite, and the correct alternatives. Only minor gaps remain, such as what 'ranked' means or how empty results differ from errors.

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 fully documented with ranges, defaults, and examples. The description adds no parameter-level semantics such as how results are ranked or how LTV is computed, so the baseline 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 identifies the exact resource — Spanish Catastro/BOE judicial real-estate auctions — and frames the tool as a 'compatibility bridge'. It also distinguishes itself from siblings by naming search_tenders and find_funded_companies as the Italy-record alternatives. It loses a point because the operative verb is ambiguous; it never plainly says 'screen/rank auctions matching filters' and leads with payment/routing plumbing instead.

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?

It gives an explicit prerequisite (DATAX_BASE_URL must point to datax-spain-eu-mcp) and an explicit when-not-to-use with named alternatives ('prefer search_tenders or find_funded_companies for Italy records'). The failure mode of ignoring this guidance (always empty matches) is spelled out, so the agent can route correctly without inference.

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