Skip to main content
Glama

Search new developments

search_developments
Read-onlyIdempotent

Use this when someone wants new developments or new build sites in an area, including those coming soon: each development with its builder, "from" price over the homes for sale, homes for sale, reserved and coming soon, bedrooms and types, and its page address. Takes the same filters as search_homes; with filters, each development says how many of its homes match and from what price.

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

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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds behavioral context: results aggregate homes per development, filtered calls report how many homes match and from what price, and coming-soon developments are included. It omits pagination limits and result totals, so it adds moderate value rather than rich context.

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 usage trigger, then the result payload and filter behavior. The result-field enumeration is dense but earns its place because there is no output schema. Slightly long, but no filler.

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 read-only search with no output schema, the description supplies the result shape (builder, from price, state breakdown, bedrooms/types, page address) and filter semantics, which an agent needs in order to call it correctly. Missing detail on pagination behavior and on resolving ambiguous place matches keeps it just short of complete.

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 71%, with detailed per-parameter text for place, types, offers, include, schools and within_miles. The description adds the high-level rule that it 'takes the same filters as search_homes' and explains how filters change the output (match counts and from-price), which is real semantic value. It does not clarify the undocumented parameters such as min_price/max_price, sort, or reduced, so compensation is partial.

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 states a specific verb and resource ('new developments or new build sites in an area') and enumerates exactly what each result contains: builder, from price, homes for sale/reserved/coming soon, bedrooms and types, and page address. It also distinguishes itself from search_homes by noting it takes the same filters but reports per-development match counts and starting prices.

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 explicitly frames the trigger: 'Use this when someone wants new developments or new build sites in an area, including those coming soon.' It also names search_homes as the filter-parity reference, signalling how the sibling relates. It stops short of stating when not to use it or naming alternatives for individual home searches, which caps it at 4.

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