Skip to main content
Glama

Get LPA Adapter Status

get_lpa_adapter_status
Read-onlyIdempotent

Purpose: 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

NameRequiredDescriptionDefault
site_refNoCanonical 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

NameRequiredDescriptionDefault
queryNo
statusYes
detailsNo
messageNo
sourcesYes
headlineYes
site_refYes
retryableNo
error_codeNo
atlasly_linkYes
error_sourceNo
human_messageNo
key_data_pointsYes
top_constraintsYes
confidence_notesYes
executive_summaryYes
next_best_actionsYes
top_opportunitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent and non-destructive; the description adds real context beyond that by disclosing that status is telemetry rather than a completeness guarantee and that live LPA portals can return sparse or unstable results. It doesn't cover permissions or refresh/caching cadence, which limits it to a 4.

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?

Labeled sections (Purpose / When to use / Returns / Limitations / Parameter guidance / Chaining) make it scannable and front-loaded with the core purpose. It runs long, and the Returns enumeration overlaps the existing output schema, so a sentence or two could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema and full annotation coverage, the description supplies everything an agent still needs: when to use it, its limitation as telemetry, the chaining contract for site_ref, and the sibling alternative. No decision-relevant gap remains.

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 baseline is 3, but the description adds non-obvious semantics: 'takes no parameters; site_ref is accepted for chaining but does not filter the result.' That prevents an agent from expecting site-level filtering and is genuine value 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?

Opens with a specific verb and resource: inspecting top-LPA planning source adapter coverage, operational status, cache state, record counts and geometry coverage. It also names the sibling (get_official_source_adapters) that covers the adjacent case, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'When to use' statement for local-adapter registrations and operational state, plus exclusions: development-site application cells and planning evidence readiness do not query these adapters. It also routes the non-UK official-source case to get_official_source_adapters by name.

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