stream-estate

Official

Overview Schema Source Related Servers Discussions Admin

find-similar-properties

Find properties similar to a reference property for market comparisons and alternative options. Filter by creation date, price, surface area, and more.

Instructions

Find properties similar to a given property. Useful for market comparisons and finding alternatives.

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": {
      "id": "<id>"
    },
    "name": "find-similar-properties"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Reference property UUID
`page`	No	Page number (default: 1)
`fromDate`	No	Creation start date (ISO 8601)
`itemsPerPage`	No	Items per page (max: 30)
`orderByPrice`	No	Sort by price
`orderBySurface`	No	Sort by surface area
`orderByCreatedAt`	No	Sort by creation date
`orderByUpdatedAt`	No	Sort by last update date
`orderByPricePerMeter`	No	Sort by price per m²

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Jul 31, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the high-level action without explaining what 'similar' means, how results are ordered, or any side effects. This is a significant gap for a tool with pagination and sorting parameters.

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?

The description is concise, with the core action front-loaded in the first sentence. The second sentence adds usage context but is somewhat generic. Overall, it is appropriately sized without unnecessary verbosity.

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

Completeness2/5

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

With no output schema and 9 parameters, the description should explain what results look like and how similarity is determined. It only states 'find properties similar' without detailing the return structure, pagination behavior, or sorting options, leaving significant gaps for the agent.

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 coverage is 100%, so the baseline is 3. The description does not add parameter-level meaning, but the schema already documents all 9 parameters including the required 'id' field. No further compensation is needed.

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 description specifies a clear verb ('Find') and resource ('properties similar to a given property'), differentiating it from siblings like search-properties (general search) and get-property (single property by ID). It uniquely identifies the tool's purpose for similarity-based lookup.

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?

The description provides context by stating the tool is 'useful for market comparisons and finding alternatives,' which implies when to use it. However, it does not explicitly mention alternatives or when not to use it, falling short of a 5.

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

Deploy Server