GetMovely

Freehold or leasehold check

tenure_check

Read-onlyIdempotent

Whether homes matching an address are freehold or leasehold, from the tenure recorded on the latest Land Registry sale of each exact address, with that sale's date. Up to 12 candidates; null tenure means no recorded sale with a tenure. Matching is by text: when fuzzy is true or the rows are not the address asked for, use search_addresses, whose rows carry tenure_at_last_sale for the exact home.

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": {
      "query": "<query>"
    },
    "name": "tenure_check"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Address or street with postcode, e.g. '12 Church Lane, BS7 8AB'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive lookup, so the safety profile is covered. The description does add real behavior: the data source (latest recorded Land Registry sale), the cap of 12 candidates, and that null tenure means no recorded sale with a tenure. It doesn't say how matches are ranked or ordered, which matters for a text-matching lookup.

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 purpose and data source are front-loaded, then the cap and null semantics, then the fallback. Dense but nearly every clause carries information; the final `fuzzy` clause is the one passage that reads as tangled.

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?

There is no output schema, and the description compensates by explaining the two returned concepts (tenure and the sale date) plus the null case and the 12-row cap. It leaves 'candidates' undefined — whether they are duplicate address matches or separate homes is not spelled out.

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 coverage is 100% and there is a single, well-exemplified query parameter, so the baseline is 3. The description doesn't add format or matching semantics for `query` beyond noting matching is textual, and its mention of `fuzzy` refers to a different tool's parameter, which can confuse rather than clarify.

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 states a specific resource (freehold/leasehold tenure for a matched address), its exact provenance (tenure recorded on the latest Land Registry sale of each exact address) and its scope (up to 12 candidates). That is enough for an agent to distinguish it from search_addresses or price_check without opening another schema.

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?

It gives an explicit alternative and trigger: if rows don't match the address asked for, use search_addresses, which carries tenure_at_last_sale per exact home. The reference to `fuzzy` being true is ambiguous because fuzzy is not a parameter of this tool, which slightly blunts the routing rule.

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?