Skip to main content
Glama

What Property calculators and area figures

Area market figures

area_market
Read-only

Free. A UK area's property market from the Market Atlas, for a council, a town, a postcode district (SR4) or a full postcode: median prices by type, ONS rents by bedrooms, gross yields, house price growth over 1, 5 and 10 years, sales, where it ranks in its region and Great Britain, the local housing allowance, its towns and postcode districts with their own medians, a postcode's own sector and district sales, and landlord rules (HMO Article 4, selective licensing), with the area's page url. Great Britain only; Scotland's prices are index averages.

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": {
      "place": "<place>"
    },
    "name": "area_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesA council ("Sunderland", "County Durham"), a town ("Bedworth"), a postcode district ("NE11") or sector ("SR4 7"), or a full postcode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely non-structured context: the tool is free, coverage is Great Britain only, and Scotland's prices are index averages rather than true medians — a data-quality caveat an agent cannot get elsewhere. It stops short of stating response shape or pagination, but with no output schema the field enumeration largely substitutes for that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one long run-on sentence that strings roughly a dozen returned fields together with commas, which makes it dense to scan. The cost note is front-loaded, but the field list would be far more usable as a structured enumeration. Every clause is informative, so little is truly wasted — it is over-packed rather than padded.

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 carries the burden of explaining return values and does so comprehensively: prices, rents, yields, growth horizons, sales, rankings, LHA, sub-areas, and landlord rules, plus a page URL. Combined with the GB-only scope and Scotland caveat, an agent knows enough to call this correctly, though it does not say what happens for an unrecognized or out-of-GB place.

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% and the single parameter already documents the accepted place forms with examples ('Sunderland', 'NE11', 'SR4 7'). The description restates the same categories rather than adding format rules, disambiguation between a town and a council of similar name, or behavior for ambiguous inputs. Baseline 3 applies.

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?

The description names the exact resource (a UK area's property market data from the Market Atlas) and the input granularities it accepts (council, town, postcode district, full postcode), so an agent can tell it apart from list_calculators, rank_areas, and run_calculator. It lacks an explicit verb like 'get' or 'fetch', opening instead with the cost note 'Free.', but the resource is unambiguous.

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 only implied: an agent can infer this is the lookup for area-level market figures, and the geographic limit 'Great Britain only' functions as a when-not condition. There is no explicit routing to or away from siblings, no statement of when rank_areas or run_calculator would be preferable.

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