GetMovely

Check a price against the district and the street

price_check

Read-onlyIdempotent

Is a price in line? Works out the price per square metre from the home's EPC floor area and sets it against three things: what homes of the same type sold for per square metre in the same postcode district in the latest whole year, with the quartiles; recent sales on the home's own street or postcode; and the home's own last sale moved by the district's change since. Also gives the price range the district's quartiles imply for this floor area. Arithmetic on public medians, not a valuation, and the answer carries the caveats to pass on. Shares the address report's limit of 60 an hour per caller.

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": {
      "akey": "<akey>"
    },
    "name": "price_check"
  }
}

Input Schema

Name	Required	Description	Default
`akey`	Yes	Address key from search_addresses (hex string).
`price_gbp`	No	The price to check, in pounds: an asking price, an offer, a valuation. Leave out to get what the district's prices imply for a home this size (and, when the home is advertised for sale, to check its asking price).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the description is free to add value — and it does: it discloses the arithmetic basis (public medians, quartiles, district change since last sale), that the output is not a valuation and carries caveats to pass on, and a hard rate limit of 60 calls/hour per caller. What's missing is any indication of response shape or failure modes, which matters since there is no output schema.

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 leads with the decision question ('Is a price in line?') and then enumerates the three benchmarks, so the reader is oriented immediately. The middle sentence is long and dense with enumerated clauses, which costs a little readability, but no sentence is 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 two-parameter read-only analytic tool with no output schema, the description covers what is computed, what data sources underpin it, the limits on certainty, and the rate limit. The only real gap is the shape of the returned comparison structure, which the agent cannot learn from either the description or a schema.

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 baseline is 3; the description earns one more point by explaining that the size denominator comes from the home's EPC floor area rather than a passed-in parameter, and by describing what the price range output represents when no price is supplied. It does not restate the akey format, but that is already fully documented.

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 states a concrete operation — computing price per square metre from the EPC floor area and benchmarking it against district-type comparables, street sales, and the home's own last sale — which an agent can distinguish from single-purpose siblings like district_statistics or street_price_per_m2. Differentiation is implicit (it consumes what those tools report) rather than stated outright, so it falls short of a 5.

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: it's clear the tool answers 'is this asking price reasonable for this home', and the schema covers the optional price. There is no explicit statement of when to choose this over district_statistics or street_price_per_m2, or what prerequisites (e.g. the address must have an EPC) apply.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GetMovely tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?