Skip to main content
Glama

Search new build homes

search_homes
Read-onlyIdempotent

Use this when someone wants new build homes, new builds or new homes for sale in a place: by price, bedrooms, house, flat or bungalow, house builder, part exchange or another builder offer, price reductions, or schools nearby. Returns the number of matching homes and developments, the homes on this page (price, status, bedrooms, bathrooms, floor area, tenure, the builder offer, the date each was checked and its page address), and a link to the same search on newhomesearch.co.uk. Only homes for sale today unless include asks for more. New build homes only: not resale homes or rentals.

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_homes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of results, from 1.
sortNorecommended
limitNo
placeNoWhere to search: a town, city, county, council area, postcode district or full postcode. A full postcode searches within 10 miles of it unless within_miles says otherwise. Leave out only to search the whole UK.
typesNohouse covers every house type; flat includes maisonettes.
offersNoOnly homes whose builder states one of these offers, for example part_exchange, stamp_duty_paid or deposit_contribution.
builderNoA house builder, as the buyer named it.
includeNoAlso show homes in these states. By default only homes for sale today are shown.
reducedNoOnly homes reduced in price since first listed.
schoolsNoOnly homes within reach of at least one school of each kind asked: kind any, primary, secondary, grammar or independent; grade outstanding or good; results top10, top25 or above (DfE results against England). England only.
any_offerNoOnly homes with an offer of any kind.
max_priceNo
min_priceNo
max_bedroomsNo
min_bedroomsNo0 is a studio.
place_optionNoWhich of several places with that name, by the option number a previous call returned.
within_milesNoSearch within this many miles of the place rather than inside its boundary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the default exclusion of coming_soon/reserved/sold_stc, the new-builds-only constraint, and exactly what the response contains (counts, per-home fields, dated checks, and a deep link).

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 sentences, front-loaded with the triggering condition, and every clause carries filter or scope information rather than filler. The long enumeration in the first sentence is dense but purposeful; nothing is redundant with the title or annotations.

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 17-parameter, zero-required search tool with no output schema, the description covers the critical unknowns: scope limits, default state filtering, and a full account of what the response returns. Remaining gaps are minor operational details like pagination limits and sort behavior, which the schema already constrains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 17 parameters and 71% schema coverage, the schema does most of the work, but the description still contributes meaning: it names the filter families (price, bedrooms, type, builder, offer, reductions, schools) and explains the include parameter's override of the default 'for sale today' behavior. It leaves page, limit, sort, place_option and any_offer entirely to the schema, so it is not fully compensatory but is above baseline.

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 opens with a specific verb-and-resource framing ('wants new build homes, new builds or new homes for sale in a place') and enumerates the filterable dimensions (price, bedrooms, type, builder, offers, reductions, schools). It explicitly bounds the scope with 'New build homes only: not resale homes or rentals', so an agent can tell this apart from resale/rental search tools without opening the schema.

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?

It clearly states when to reach for this tool and adds a when-not condition ('not resale homes or rentals') plus the default visibility rule ('Only homes for sale today unless include asks for more'). It does not explicitly route to a sibling such as search_developments even though it also returns development counts, leaving a small ambiguity about which tool to pick for a development-led query.

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