FindEstate Real Estate

get_project

Read-onlyIdempotent

Read the explicitly published factual project summary, including sources and geographic precision. An empty listing array does not mean the project has no units. Project ranges are not individual unit prices.

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>"
    },
    "name": "get_project"
  }
}

Input Schema

Name	Required	Description	Default
`catalogId`	Yes	Catalog ID from a public catalog link. MCP access is checked independently of GEO visibility.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the data-provenance note ('explicitly published factual') and the two output caveats about empty listing arrays and price ranges. That is genuine context beyond the annotations, but it omits anything about scoping, permissions, or response shape.

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 short sentences with the purpose front-loaded and no filler; each caveat is stated tersely. 'Including sources and geographic precision' is slightly opaque phrasing, but nothing is wasted.

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?

With no output schema, the description carries the burden of explaining returns; it partially does so by naming the listing array, price ranges, sources, and geographic precision. It still leaves the overall response shape and any nesting unexplained, which matters for an agent that must consume the result.

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 100% for the single catalogId parameter, including its UUID pattern and the note that MCP access is checked independently of GEO visibility. The description adds no meaning about catalogId, so the baseline 3 applies.

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 clear verb+resource: 'Read the explicitly published factual project summary,' and adds that the payload includes sources and geographic precision. It does not, however, distinguish this 'project' resource from siblings like get_property or get_findestate_property, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no statement of when a project lookup is preferable to get_property or search_properties, and no prerequisites beyond what the schema already says about catalogId. The two caveats present concern interpreting results, not selecting the tool.

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?