Skip to main content
Glama

DealScreener: Spanish property auctions

Ver la ficha de un inmueble

get_deal
Read-onlyIdempotent

Devuelve la ficha pública de un inmueble cribado por su key (la que da search_auctions): veredicto y puntuación, qué es, rangos de superficie, precio o puja mínima y €/m², datos comprobados y pendientes, avisos, puja máxima orientativa en rango cuando la hay, y el enlace a la ficha en dealscreener.io. Solo cribado, no asesoramiento.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>"
    },
    "name": "get_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesKey de 14 caracteres de search_auctions (o del enlace dealscreener.io/deal?k=...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description goes further by enumerating exactly what the record contains: veredicto y puntuación, rangos de superficie, precio o puja mínima, €/m², datos comprobados y pendientes, avisos, puja máxima orientativa and the outbound link. That payload disclosure matters because there is no output schema, and the 'no asesoramiento' line sets an expectation about the nature of the content.

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?

Purpose is front-loaded in the first clause and the long enumeration of returned fields is dense but earns its place given the missing output schema. The scope disclaimer is a compact final clause; the sentence is lengthy but not padded.

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?

With one fully documented parameter and no output schema, the definition covers what an agent needs: how the key is obtained, what will come back, and the limit that this is screening rather than advice. Nothing material is left to inference for a read-only lookup.

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% and the single parameter already documents both the 14-character format and the dealscreener.io/deal?k=... alternative. The description restates that the key comes from search_auctions but adds no format, validation or edge-case detail beyond what the schema provides, 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 a specific verb (devuelve) and a specific resource (la ficha pública de un inmueble) retrieved by key, and names search_auctions as the source of that key, so the agent can separate it from the search tool without opening the schema.

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?

The description ties the tool to search_auctions as the origin of the key, which implies the retrieve-after-search workflow, and adds the scope caveat 'Solo cribado, no asesoramiento'. It stops short of an explicit when-not or of naming conditions that would rule this tool out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources