Get LPA Adapter Status
get_lpa_adapter_statusPurpose: inspect Atlasly top-LPA planning source adapter coverage, operational status, cache state, record counts, and geometry coverage. When to use: use when inspecting local-adapter registrations and reported operational state. Development-site application cells and planning evidence readiness do not query these adapters. Returns: registered adapters, adapter type, manual-check status, cache timestamps, cached record counts, geometry coverage percentages, sources and next actions. Limitations: status is operational telemetry, not a completeness guarantee for every address or proposal; live LPA portals can still return sparse or unstable result sets. For official-source adapters outside UK local planning authorities, use get_official_source_adapters. Parameter guidance: takes no parameters; site_ref is accepted for chaining but does not filter the result. 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
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": "get_lpa_adapter_status"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| 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. |
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 |