Skip to main content
Glama

Coverage At A Location

get_location_coverage
Read-onlyIdempotent

Check registered context/place routes and selected official research references for a supplied global WGS84 point and country before choosing a task. No geocoding, dataset retrieval or source health probe. Separates community geometry, configuration and document references from unassessed local zoning, parcel intersections and statutory applicability. A registered source is not evidence of coverage or no risk. Returns a coverage register and Atlas AI UI; known coordinates required. 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": {
      "country_code": "<country_code>",
      "coordinates": "<coordinates>"
    },
    "name": "get_location_coverage"
  }
}

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.
coordinatesYesUser-supplied WGS84 point {lat, lng}. Send with country_code. The point is not reverse-geocoded, so its address and planning jurisdiction stay unverified.
country_codeYesISO two-letter country code such as gb, us, in or fr. Required with coordinates and for addresses outside the UK.

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. Changed2 schema fields changed
    • addedInput schema / properties / coordinates / description
      Added value: +"User-supplied WGS84 point {lat, lng}. Send with country_code. The point is not reverse-geocoded, so its address and planning jurisdiction stay unverified."
    • addedInput schema / properties / country_code / description
      Added value: +"ISO two-letter country code such as gb, us, in or fr. Required with coordinates and for addresses outside the UK."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds real context beyond that: the 'registered source is not evidence of coverage or no risk' caveat, the separation of community geometry from unassessed zoning/parcel/statutory data, the requirement for known coordinates, and the response shape. This is meaningful disclosure for a pre-assessment tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, but the description is dense and jargon-heavy. 'Separates community geometry, configuration and document references from unassessed local zoning, parcel intersections and statutory applicability' is opaque, and 'Returns a coverage register and Atlas AI UI' is awkward. Every sentence contributes something, but the phrasing is not tight.

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 an output schema present, the description needn't detail return values, and it still covers usage context, exclusions, a critical caveat (source registration ≠ coverage), and the site_ref chaining contract. Given the rich schema and annotations, an agent has enough to invoke this correctly, though the abstract middle sentence leaves some ambiguity about what 'coverage' means.

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 description coverage is 100%, so all three parameters are already documented in the schema. The description adds only a mild restatement ('known coordinates required') and repeats the site_ref chaining rule already covered by the schema's site_ref description. Baseline 3 applies when the schema does the heavy lifting.

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 opens with a specific verb+resource: checking registered context/place routes and official research references for a point, framed as pre-task triage ('before choosing a task'). It implicitly distinguishes from geocoding and dataset-retrieval siblings via exclusions, but never names a sibling tool, so an agent must infer the boundary.

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?

It gives a clear usage context ('before choosing a task') and explicit exclusions ('No geocoding, dataset retrieval or source health probe'), which steers an agent away from sibling tools like get_official_source_adapters. It lacks an explicit 'use X instead' routing statement, so it falls short of a 5.

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