Skip to main content
Glama
Sign In

GetMovely

by uk.co.getmovely
OverviewDiscussionsAdmin

Search the guides

search_guides
Read-onlyIdempotent

GetMovely's plain-English guides to buying and selling homes in England and Wales: contacting an owner directly and the law on it, buying or selling without an estate agent, finding who owns a property or the address behind a listing, how often sales fall through, speeding a sale up, best and final offers, stopping unwanted letters. Returns the closest guides with a one-paragraph summary and the questions each answers; read_guide gives the full text with its sources.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWhat the person wants to know, in plain words: 'is it legal to write to a homeowner', 'who owns the freehold', 'how many house sales fall through'. Leave out to list every guide.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add retrieval behavior — and it does: results are the 'closest' guides (relevance-ranked, not exhaustive), each with a one-paragraph summary plus the questions it answers. That is genuinely useful expectation-setting. It stops short of stating result count limits or ranking/fallback behavior when nothing matches.

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?

Two sentences, front-loaded with the resource and scope, with the sibling routing in the final clause. The mid-sentence topical enumeration is long but each item earns its place by telling the agent what the corpus covers, which is essential for query formulation. Slightly dense, not wasteful.

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?

With one optional parameter, no nested objects, and no output schema, the description does need to explain what comes back — and it does (closest guides, summary paragraph, questions answered). Combined with annotations and a fully documented parameter, an agent has enough to call this correctly. Minor gap: no sense of result volume or ranking strength.

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 the parameter description already includes example phrasings and the 'leave out to list every guide' behavior, so the schema carries the semantics. The description adds topic scope that helps the agent phrase a query, but nothing about the query string itself. Baseline 3 is appropriate.

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 names the resource (GetMovely's plain-English guides to buying/selling homes in England and Wales), enumerates the covered topics, and states the return shape ('the closest guides with a one-paragraph summary and the questions each answers'). It also explicitly differentiates itself from read_guide ('read_guide gives the full text with its sources'), so an agent can tell the two apart. It loses a point only because no single verb frames the operation up front — the retrieval nature is inferred from 'Returns the closest guides'.

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?

Guidance is given: use this to locate relevant guides by topic, then use read_guide to get full text with sources. The two-step workflow is implied clearly enough to act on. There is no explicit 'do not use this for X' exclusion, and no statement about what happens when no guide matches, which keeps it below a 5.

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