Skip to main content
Glama

Find Discounted Real-Estate Auctions

find_distressed_auctions
Read-onlyIdempotent

Find discounted Spanish judicial and notarial property auctions ranked by debt-to-value ratio and equity margin, with Catastro valuation data and province/LTV filters.

Instructions

Screen official Spanish judicial and notarial real-estate auctions enriched with Catastro valuation data, ranked ascending by debt-to-value ratio (ltv_pct) and equity margin. Costs $0.10 USDC or EURC per call via DATAX_TOKEN (returns HTTP 402 if unset). Returns masked auction previews and opaque item_ref handles ('dx_...') unlockable via get_tender_detail ($0.50). Use this specifically to discover discounted Spanish property auctions; use search_tenders for non-auction 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.2
    • 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.5/5.0
Behavior5/5

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

Annotations already state readOnly/idempotent/non-destructive, and the description adds behavior they cannot express: a per-call charge of $0.10 USDC/EURC gated by DATAX_TOKEN with an HTTP 402 failure mode when unset. It further discloses that results are masked previews plus opaque 'dx_...' handles that cost $0.50 to unlock, which directly shapes how an agent should budget and sequence calls.

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?

The first sentence front-loads scope and ranking, and the alternatives sentence closes it out; nearly every clause carries load-bearing information. It is dense to the point of cramming payment, masking, and unlock pricing into a single middle sentence, but no sentence is disposable.

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 does not need to restate return fields, yet it still explains the masked-preview and item_ref mechanics that determine next steps. Combined with pricing, auth failure mode, and sibling routing, an agent has what it needs to call this correctly; only the exact unlock handoff fields via get_tender_detail remain implicit.

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 coverage is 100%, so every parameter (limit, ambito, max_ltv_pct, min_value_eur, concursal_only) is already documented in the schema, meeting the baseline of 3. The description adds only the directional cue that the list is ranked ascending by ltv_pct, which helps interpretation but does not deepen any individual parameter's meaning.

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?

Opens with a specific verb-plus-resource ('Screen official Spanish judicial and notarial real-estate auctions') and states the enrichment source (Catastro) and ranking key (ltv_pct, equity margin), which no sibling exposes. The final sentence explicitly names search_tenders as the non-auction alternative, so an agent can separate the two without reading 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?

Gives an explicit when-to-use ('to discover discounted Spanish property auctions') and an explicit when-not ('use search_tenders for non-auction records'). It also routes the follow-up step to get_tender_detail for unlocking item_ref handles, covering the full workflow decision, not just the first call.

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