FindEstate Real Estate

Show FindEstate cards

render_findestate_properties

Read-onlyIdempotent

Display up to ten previously returned FindEstate offer/project references as interactive cards. For a comparison request use compare_properties instead; it rereads current facts and opens its own comparison. This reference-only tool does not preserve the search filters that selected the references. For a map request, call search_findestate_map directly with the full requested filters and locale; do not render cards after that map tool. Pass only exact kind, catalogId and id references, plus locale. Every reference is fetched again through current GEO and MCP permission checks; never pass arbitrary card objects, text, image URLs or third-party links. Project images are labeled project imagery and are not photographs of a specific unit. Individual property cards include Request a viewing and I have questions actions with short guest forms inside ChatGPT. No FindEstate account is needed. Opening cards or a form sends no contact details and creates no request; the person must explicitly send. No property reservation, confirmed appointment, checkout or payments.

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": {
      "items": "<items>"
    },
    "name": "render_findestate_properties"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes
`locale`	No		en

Output Schema

Name	Required	Description	Default
`asOf`	No
`items`	Yes
`status`	Yes
`filters`	Yes
`hasMore`	No
`version`	Yes
`coverage`	Yes
`browseUrl`	Yes
`nextCursor`	Yes
`totalCount`	No
`resultSetCount`	No
`totalCountRelation`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), but the description adds substantial context beyond them: every reference is re-fetched through current GEO and MCP permission checks, arbitrary card objects/text/URLs are rejected, project images are labeled imagery rather than unit photographs, and in-card forms send nothing until the user explicitly submits. The closing sentence rules out reservations, appointments, checkout and payments, which is exactly the kind of scope boundary an agent cannot infer 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?

Purpose and the two sibling alternatives are front-loaded, and the remaining sentences are dense with behavioral constraints rather than filler. It is long and a few clauses (guest forms, no account needed) could be tightened, but nearly every sentence carries decision-relevant information.

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 an output schema present, return values need no explanation, and the description covers what remains: input provenance, permission re-checks, the ten-item limit, and the absence of side effects on open. Nothing an agent needs in order to call this correctly or to explain it to a user is missing.

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

Parameters4/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 the load: it states that only exact kind, catalogId and id references plus locale may be passed, and that they must come from previously returned results — semantics the bare JSON schema does not convey. It does not spell out the meaning of the locale enum or the property/project kind values, which the enum schema partially covers, leaving a small gap.

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?

The first sentence gives a specific verb (Display), a bounded resource (up to ten previously returned FindEstate offer/project references), and the output form (interactive cards). It explicitly separates this tool from compare_properties and search_findestate_map by naming both siblings and the conditions that select them.

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 routes the agent three ways: comparison requests go to compare_properties, map requests go to search_findestate_map with full filters and locale, and cards are explicitly not to be rendered after the map tool. The constraint that this tool does not preserve search filters tells the agent when it must re-search instead.

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

All FindEstate Real Estate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?