Skip to main content
Glama
joemclo

Property Price Search MCP Server

by joemclo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
search-property-pricesA

Search HM Land Registry price-paid data. Provide either postcode or both street and city (case-insensitive; uppercased for the query). Optional filters: minPrice/maxPrice (GBP), propertyType (detached | semi-detached | terraced | flat | other), fromDate/toDate (YYYY-MM-DD), limit/offset (pagination), sortBy (date | price), sortOrder (asc | desc). Returns JSON: { properties: [{ price, date, postcode, propertyType, street, city, paon?, saon? }], total, offset, limit }, where paon is the Primary Addressable Object Name (e.g., house number/name) and saon is the Secondary Addressable Object Name (e.g., flat/unit/apartment).

lookup-postcodesA

Look up UK postcodes (Code-Point Open) and find nearest neighbours using OSGB36 eastings/northings. Provide either postcode or both easting and northing as the center. Optional: radiusMeters (meters), limit (default 10), includeSelf (default false), adminDistrict filter. Returns { center, postcodes: [{ postcode, easting, northing, positionalQuality, countryCode, adminDistrictCode, distanceMeters }], total }. Requires a local database built from the bundled codepo_gb CSVs via npm run build:postcodes.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one looks up postcode data and finds nearest neighbours, while the other searches property price data. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with hyphens: 'lookup-postcodes' and 'search-property-prices'. This naming convention is predictable and readable throughout the set.

Tool Count2/5

With only 2 tools, the server feels under-scoped for a property price search domain. While the tools cover postcode lookup and price search, there are likely missing operations such as filtering by property features or retrieving detailed property records, making the surface thin and incomplete.

Completeness2/5

The server lacks comprehensive coverage for property price search. It includes basic lookup and search functions but misses essential operations like updating or deleting data, advanced analytics, or integration with other property databases, which could lead to agent failures in complex tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources