Skip to main content
Glama
Sign In

GetMovely

by uk.co.getmovely
OverviewDiscussionsAdmin

Overview of one postcode district

area_overview
Read-onlyIdempotent

What homes sell for in one postcode district, for every property type sold there (detached, semi-detached, terraced, flats): the latest whole year's median price per square metre with its quartiles and number of sales, the change since the series began in 2015, and the year in progress against the same months a year earlier. Use compare_areas to set districts against each other and price_trends for what tenure, energy rating or size are worth within one.

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": {
      "outcode": "<outcode>"
    },
    "name": "area_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
outcodeYesPostcode district such as 'SW19', 'BS7', 'M6'. A full postcode is accepted; only the district is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond those annotations by specifying the time windows, property-type scope, and statistical contents returned.

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?

The description is front-loaded with purpose and uses a second sentence for routing to alternatives. The first sentence is long and dense, but every clause carries substantive information about what the tool returns.

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?

Given the absence of an output schema, the description adequately explains what data is returned, including property types, metrics, and time periods. It could clarify edge cases such as missing property types or data freshness, but it is complete enough to call the tool correctly.

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 schema already explains that the outcode parameter accepts a full postcode but only the district is used. The description reinforces the district scope but adds no syntax or format details beyond the schema.

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 clearly states the resource (one postcode district) and the specific contents: prices by property type, median price per square metre, quartiles, sales counts, change since 2015, and year-in-progress comparison. It also names sibling tools it is not, so an agent can distinguish it without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent to compare_areas for cross-district comparison and price_trends for tenure/energy/size value within one district. The first sentence defines the scenario this tool serves: an overview of one district across property types and time.

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

All GetMovely toolsInspect
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