Skip to main content
Glama

GetMovely

Compare two to four homes

compare_homes
Read-onlyIdempotent

Two to four homes side by side, one row each: type and floor area, tenure, last sale and its price per square metre, energy rating and modelled running cost, what the street has sold for recently, the district trend, whether it is owner-occupied, whether it is listed for sale and its response likelihood (High = both), the nearest supermarket, primary school, station and park, recorded crime and air quality. Each row links its own report and the page that opens a letter to its owner. Counts as one address report per home against the 60 an hour limit.

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": {
      "akeys": "<akeys>"
    },
    "name": "compare_homes"
  }
}

Input Schema

NameRequiredDescriptionDefault
akeysYesTwo to four address keys from search_addresses.

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 read-only, idempotent, closed-world and non-destructive behavior, so the description needn't repeat safety. It does add genuinely non-obvious traits: the quota accounting (one report per home against a 60/hour limit), and that each row carries links to its own report and to an owner letter page.

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 the core comparison promise and the row semantics, then the output fields, then cost. The field enumeration is long but earns its place because no output schema exists; a little tightening of the run-on middle clause would help.

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 no output schema, the description does the necessary work of spelling out the returned per-row fields and how rows link out. Only minor gaps remain, such as behavior when a key is invalid or an address has no data.

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 single akeys parameter is fully documented in the schema, including the hex pattern and the 2-4 item bounds. The description's 'two to four homes' merely restates those bounds and adds no key syntax or validation detail 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?

States a specific verb and resource ('compare ... side by side, one row each') and enumerates the compared dimensions in enough detail that an agent can distinguish it from address_report and compare_areas 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 'two to four homes side by side' framing implies this is the multi-address option versus a single address report, and the cost note ('one address report per home') gives practical usage context. However, it never explicitly says when to use this instead of address_report or compare_areas.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources