Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rightmove_autocomplete

Get Rightmove location autocomplete suggestions for a query and return IDs to use as location values in property searches.

Instructions

Get Rightmove location autocomplete suggestions. Returns Rightmove location suggestions for the required query (up to 200 characters). limit defaults to 10 and is capped at 20. Each result has an id such as REGION^87490, a name, a full_name when Rightmove gives one, and an entity_type such as REGION or POSTCODE. Use the id as location in Rightmove search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum suggestions to return (default 10, max 20)
queryYesLocation query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (id, name, full_name, entity_type), the id format (`REGION^87490`), and the hard cap on results. It does not explicitly state it is a side-effect-free read, but an autocomplete endpoint makes that implicit.

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?

Front-loaded with purpose, then constraints, then result shape, then the downstream hand-off. Every sentence earns its place, though the result-field enumeration is slightly verbose relative to the rest.

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?

No output schema exists, so the description rightly documents the returned fields and id format, and it covers both parameters and the intended downstream use. It is complete enough to call correctly, missing only explicit safety/read-only framing.

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 the baseline is 3, and the description earns one step above by adding the 200-character constraint on `query` that the schema does not state. The limit default/cap detail restates what the schema already documents, so it adds no new value there.

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?

States a specific verb and resource ('Get Rightmove location autocomplete suggestions') and clarifies its role in the pipeline by naming the sibling it feeds ('Use the `id` as `location` in Rightmove search'). An agent can tell this is a typeahead helper rather than a search tool without opening the schema.

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?

The downstream instruction ('Use the `id` as `location` in Rightmove search') implies when the tool is useful, but there is no explicit when-to-use vs when-not guidance or comparison against alternatives like rightmove_search. Usage is inferable but not spelled out.

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

Deploy Server

Other Tools