Compare Two Sites
compare_sitesPurpose: compare exactly two UK sites for the same intended use and stage using the existing Site Verdict evidence. When to use: use after appraising one or two candidate sites, or when an architect/developer needs a shortlist decision that colleagues can review. Returns: both canonical site_ref objects, verdicts, potential dealbreakers, design-changing risks, visible unknown asymmetry, a transparent preferred-site decision only when one site dominates, both static map links, sources, and a temporary branded decision card. Limitations: address-only inputs remain point-radius screens; missing evidence is never treated as clear; the comparison uses no hidden weighted score and does not replace acquisition, planning, or technical due diligence. Parameter guidance: pass site_a and site_b with either address or a prior site_ref, plus one intended_use and project_stage shared by both sites; optional proposal and no_go_triggers are applied equally. Chaining: every response returns site_ref; pass it unchanged into another Atlasly tool to reuse the canonical site, coordinates, boundary confidence, LPA, evidence links, and project context.
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": {
"site_a": "<site_a>",
"site_b": "<site_b>",
"intended_use": "<intended_use>",
"project_stage": "<project_stage>"
},
"name": "compare_sites"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| site_a | Yes | ||
| site_b | Yes | ||
| proposal | No | Optional shared proposal detail applied equally to both sites | |
| site_ref | No | Canonical site_ref returned by any previous Atlasly tool. Pass it unchanged to chain the same resolved site into this call; address, search_area, or project_id will be filled from it when omitted. | |
| intended_use | Yes | Shared intended use, for example residential, office, or mixed use | |
| project_stage | Yes | Shared decision stage, for example acquisition or feasibility | |
| radius_meters | No | Point-screen radius in metres; defaults to 800 | |
| no_go_triggers | No | Optional explicit no-go rules applied equally to both sites |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | ||
| status | Yes | ||
| details | No | ||
| message | No | ||
| sources | Yes | ||
| headline | Yes | ||
| site_ref | Yes | ||
| retryable | No | ||
| error_code | No | ||
| atlasly_link | Yes | ||
| error_source | No | ||
| human_message | No | ||
| key_data_points | Yes | ||
| top_constraints | Yes | ||
| confidence_notes | Yes | ||
| executive_summary | Yes | ||
| next_best_actions | Yes | ||
| top_opportunities | Yes |