Skip to main content
Glama

FindEstate Real Estate

Prepare a FindEstate guest form

prepare_findestate_enquiry
Read-onlyIdempotent

UI-only: reread the exact public property and issue a short-lived, target-bound guest submission intent. This does not submit contacts or create an enquiry. The opaque intent is delivered only to the component, not model-visible content. No FindEstate account is required.

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": "prepare_findestate_enquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
kindYes
localeYes
catalogIdYes

Output Schema

NameRequiredDescriptionDefault
statusYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses the intent's lifetime (short-lived), its binding (target-bound), its delivery channel (only to the component, not model-visible content), the absence of side effects (no contacts submitted, no enquiry created), and that no account is needed. These are non-obvious traits an agent could not infer from readOnlyHint/idempotentHint alone.

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?

Three tight sentences, front-loaded with the 'UI-only' framing and the core action, with no redundant phrasing. Slight density from stacked qualifiers ('short-lived, target-bound guest submission intent') but nothing that wastes space.

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?

An output schema exists, so return values need not be described, and the description covers side effects, prerequisites, and intent lifetime well. The clear remaining gap is that none of the four required inputs are explained anywhere, since the schema documents them at 0% coverage.

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% for all four required parameters, so the description must carry that burden, but it does not. It never explains catalogId vs id, nor what choosing VIEWING versus QUESTION as kind means for the resulting intent, nor how locale affects the form.

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?

The description states a specific action: reread the exact public property by identifier and issue a short-lived, target-bound guest submission intent. It also clearly distinguishes itself from the enquiry-creating siblings with 'This does not submit contacts or create an enquiry,' though it does not name open_findestate_enquiry or submit_findestate_enquiry directly.

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?

'UI-only' and the explicit negative scope imply this is a preparatory step rather than a submission step, which gives an agent usable context. However, it never states when this tool should be chosen over open_findestate_enquiry or submit_findestate_enquiry, or what the agent should do after the intent is issued.

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