Skip to main content
Glama

FindEstate Real Estate

Read FindEstate details

get_findestate_property
Read-onlyIdempotent

Read one previously returned offer or project by its exact reference. Rechecks both public channel permissions and current facts. Unavailable or withdrawn records are not replaced with cached facts. Asking prices, derived asking price per m², project ranges, sourced total rooms versus bedrooms, floor/year facts, observation dates and original currency retain their distinct meanings. Parent-project association is returned only when confirmed. This detail read has no query-specific match explanation. Never infer current availability from an observation date.

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": {
      "kind": "<kind>",
      "catalogId": "<catalogId>",
      "id": "<id>"
    },
    "name": "get_findestate_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
kindYes
localeNoen
catalogIdYes

Output Schema

NameRequiredDescriptionDefault
itemYes
statusYes
versionYes
coverageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses that channel permissions and current facts are rechecked, that withdrawn records are not substituted with cached facts, that parent-project association appears only when confirmed, and that observation dates must not be read as availability. These are exactly the behavioral caveats an agent cannot get from structured fields.

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?

Front-loads the core action in the first sentence and keeps the rest to scoping and caveats with no filler. The middle field-semantics sentence is dense and list-like, but each clause carries distinct meaning; slightly trimmed it would be tighter.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the annotations plus description cover the safety and freshness profile well. The gap is input-side: with a required catalogId, a kind discriminator, and a locale default, an agent still can't tell from the definition how to construct a valid call or what happens on an unavailable record.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, yet it never explains the required kind discriminator (property vs project), what catalogId scopes, or that locale selects 'lt'/'en'. Only the id is obliquely covered via 'exact reference.' This leaves three of four parameters undocumented across both schema and description.

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?

States a specific verb and resource: 'Read one previously returned offer or project by its exact reference,' which makes clear this is a single-record detail read rather than a search. The 'previously returned' scope implicitly separates it from the search_* siblings, though no sibling is named explicitly. Minor tension between the tool name ('property') and the description's 'offer or project,' resolved only by the kind enum in 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 Guidelines3/5

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

The phrase 'previously returned' plus 'by its exact reference' implies this is a follow-up call after a search, and 'This detail read has no query-specific match explanation' hints at what it will not do. However, no explicit when-to-use/when-not guidance is given relative to get_property, get_project, or get_auction, and there is no statement about what to do when the record is unavailable.

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