FindEstate Real Estate

Open a FindEstate enquiry form

open_findestate_enquiry

Read-onlyIdempotent

Show an in-chat guest form for an exact previously returned individual property: VIEWING for a preferred viewing time or QUESTION for a message. No FindEstate sign-in is required. Opening a form creates no enquiry. Ask the person to fill contacts privately in the form and explicitly press Send; do not request or echo their contact details in the conversation. Contacts are unverified; sending does not confirm an appointment, reserve a property or pay a deposit. Do not use a project summary in place of a particular unit.

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

Input Schema

Name	Required	Description	Default
`id`	Yes
`kind`	Yes
`locale`	Yes
`catalogId`	Yes

Output Schema

Name	Required	Description	Default
`item`	Yes
`status`	Yes
`version`	Yes
`enquiryKind`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing that no FindEstate sign-in is required, that opening a form creates no enquiry, that contacts are unverified, and that sending does not confirm an appointment, reserve a property, or pay a deposit. This is exactly the consequence-level context an agent needs before showing a form to a guest, and it is consistent with readOnlyHint/idempotentHint.

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 purpose and modes, then layers the privacy and non-commitment caveats, with no filler sentences. It is dense but every clause carries operational meaning; a slightly cleaner separation between the mode description and the safety rules would help scanning.

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?

For a form-opening tool with an output schema and annotations covering safety, the description covers guest-flow, privacy, and non-commitment semantics well. The main gaps are the unexplained catalogId and locale parameters and the lack of an explicit handoff to the submission step.

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 0%, so the description must carry parameter meaning; it explains 'kind' semantics (VIEWING vs QUESTION) and implies 'id' must reference a previously returned individual property. It says nothing about 'catalogId' or 'locale' (the latter has an 8-value enum the agent must choose blindly), leaving half the parameters unexplained.

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 concrete verb and resource ('Show an in-chat guest form') and scopes it to 'an exact previously returned individual property', then names the two modes (VIEWING for a preferred viewing time, QUESTION for a message). The closing admonition 'Do not use a project summary in place of a particular unit' further pins down what the tool is not for.

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?

Gives clear when-to-use guidance by mapping the two enum values to intents, plus procedural instructions (ask the person to fill contacts privately and press Send; don't echo contact details). It also clarifies that opening is not the same as submitting an enquiry. It stops short of naming any sibling tool (e.g. prepare_findestate_enquiry / submit_findestate_enquiry) as the alternative for the next step, so routing relies on inference.

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?