Skip to main content
Glama

Search properties

search_properties
Read-onlyIdempotent

Search for real estate properties by ZIP code, city, state, status, property type, price range, bedrooms, bathrooms, and more. Returns up to 25 properties per call with address, price, beds, baths, square footage, year built, listing status, and price history.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name
sortNoSort field
limitNoResults per page (1-100, default 25)
orderNoSort direction
stateNoTwo-letter state code (e.g. 'CA')
offsetNoPagination offset
statusNoListing status filter
maxBedsNoMaximum bedrooms
minBedsNoMinimum bedrooms
zipCodeNoFive-digit ZIP code (e.g. '90210')
maxPriceNoMaximum price filter
minPriceNoMinimum price filter
propertyTypeNoProperty type filter
confirmedWithinHoursNoOnly homes whose on-market status was confirmed within this many hours (e.g. 48). Each result's market.listing_confirmed_at says when.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirmedWithinHours
      Added value: +{
      +  "description": "Only homes whose on-market status was confirmed within this many hours (e.g. 48). Each result's market.listing_confirmed_at says when.",
      +  "maximum": 8760,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description usefully enumerates the returned fields, which matters because there is no output schema. However, the claim "Returns up to 25 properties per call" conflicts with the schema's limit parameter (1-100, default 25), leaving the actual result cap ambiguous.

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?

Two front-loaded sentences: capability first, return shape second, with no padding. The trailing "and more" is vague filler and the return-fields sentence is long, but both sentences earn their place given the absence of an output schema.

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?

With 14 optional parameters, no required args, no output schema, and rich annotations, the description covers the essentials: what is searched, how results can be narrowed, and what comes back. The remaining gaps are the 25-vs-100 limit discrepancy and no pagination guidance for offset, which an agent paginating results would need.

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%, so every one of the 14 parameters is already documented with types, enums, and examples; the baseline is therefore 3. The description restates several filter categories but adds no syntax, constraint, or interaction detail beyond the schema, and says nothing about sort/order/offset/limit or the confirmedWithinHours recency filter.

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?

States a specific verb and resource ("Search for real estate properties") and enumerates the filter dimensions, so the agent knows exactly what the tool retrieves. It does not differentiate itself from siblings such as lookup_property_by_address or get_property, so the agent must infer the boundary between searching and looking up a known property.

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?

Usage is implied by the filter list (use when you have criteria like ZIP, city, price, beds) but there is no explicit when-to-use statement, no when-not-to-use, and no named alternative for single-property retrieval. The agent gets a reasonable but inferred picture of when this tool fits.

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