Skip to main content
Glama

Find house builders

find_builders
Read-onlyIdempotent

Use this for which house builders are selling new homes in a place, with how many developments and homes each has there; or for one builder by name: its developments with homes for sale and prices, when it was founded, its parent group, what it says about itself, and the awards its own website lists. Give a place, a builder, or both.

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": "find_builders"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoA town, city, county, council area, postcode district or full postcode (within 10 miles of it).
builderNoA house builder by name, for example Barratt Homes or Taylor Wimpey.
place_optionNoWhich of several places with that name, by the option a previous call returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/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 safety is covered. The description's notable addition is provenance framing — 'what it says about itself, and the awards its own website lists' signals self-reported, unverified marketing data, which matters for interpretation. It says nothing about ambiguity handling when several places share a name, or about result volume/cost, leaving real gaps beyond the annotations.

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?

It is front-loaded with 'Use this for' and every clause carries distinct information — no filler sentences. However, it is a single long run-on sentence with two heavy parallel clauses, which makes it denser to parse than necessary; splitting the place-mode and builder-mode into separate sentences would improve scanability.

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 no output schema, the description takes on the burden of explaining return content, and it does so in reasonable detail for both modes (counts of developments and homes; prices, founding year, parent group, self-description, awards). What is missing is any statement of how results are shaped or how many builders are returned, and what happens on an ambiguous place name — a plausible scenario given the place_option parameter.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds one thing the schema does not: that the two main parameters are combinable and that a call should supply a place, a builder, or both. This resolves the ambiguity created by required=0 (all parameters optional), telling the agent that an empty call is not the intended usage. The place_option mechanism is only explained in the schema, not the description.

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 two concrete modes with specific verbs and resources: aggregate builder coverage for a place ('how many developments and homes each has there') and a single builder profile ('developments with homes for sale and prices, when it was founded, its parent group...'). This is clearly a builder-directory tool, distinguishable from sibling tools like search_developments or get_development, which operate on developments rather than builder entities.

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?

'Use this for which house builders are selling new homes in a place... or for one builder by name' gives an explicit use-case framing, and the closing 'Give a place, a builder, or both' specifies the valid call shapes. There is no explicit when-not guidance and no sibling alternative is named for cases where the agent wants developments or homes rather than builders, so it stops 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources