Skip to main content
Glama

What Property calculators and area figures

Rank areas

rank_areas
Read-only

Free. Ranks Great Britain's councils on one Market Atlas figure, such as the highest terrace yields in the North East under £150,000 or the fastest price growth in Wales. Each council comes with its median price, terrace yield, rent, five-year growth and page url.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many, 10 by default.
orderNohigh puts the highest first, low the lowest. By default the cheapest price, else the highest.
regionNoOnly councils in one region or country: an English region ("North East", "Yorkshire and The Humber", "London"), or "England", "Wales" or "Scotland".
measureNoWhat to rank by: terraceYield (gross yield on a typical terraced house, the default), typeYield (gross yield for propertyType's usual bedrooms), grossYield (all homes), price (median, or propertyType's), rent (average a month, or for propertyType's usual bedrooms), change1y, change5y and change10y (house price index, %), sales (in 12 months), allowanceGap (two-bed housing allowance less the average two-bed rent).
maxPriceNoOnly councils whose median price (propertyType's, when given) is at most this, in pounds.
minSalesNoOnly councils with at least this many sales in 12 months, 100 by default.
propertyTypeNoFor typeYield, price, rent and maxPrice: that type of home's figures.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond that: 'Free' discloses the cost model, and it enumerates the fields returned for each council (median price, terrace yield, rent, five-year growth, page url). It says nothing about ordering defaults or pagination, but the schema covers those.

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, no waste, with the cost signal and the ranking scope front-loaded before the illustrative examples. The one-word 'Free.' opener is terse but informative rather than 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 seven-parameter, all-optional filtering/ranking tool the description covers purpose, example invocations and the shape of returned rows, and annotations cover the safety profile. With no output schema, a brief note on result ordering or row count would close the remaining gap, but nothing essential is missing.

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%, with all seven parameters, enums and defaults documented in detail, so the baseline is 3. The description's examples implicitly illustrate combining measure + region + maxPrice, but add no format or constraint detail beyond the schema.

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 — 'Ranks Great Britain's councils on one Market Atlas figure' — with concrete examples of combining region, measure and price cap. It clearly reads as a ranking operation distinct from the calculator siblings (list_calculators/run_calculator), though it never names or explicitly contrasts with them.

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?

The two worked examples ('highest terrace yields in the North East under £150,000', 'fastest price growth in Wales') show exactly how to combine region, measure and maxPrice, which functions as practical when-to-use guidance. There are no explicit exclusions or named alternatives, so it stops short of full routing guidance.

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