Atlasly

Purpose: prepare a limited first site read. When to use: use for an initial resolved England address before selecting further evidence tools. Returns: reported flood point evidence, a bounded national application sample with explicit decision text, conditional point elevation and source gaps. Limitations: heritage, conservation, Article 4, trees, designations, landfill, ground and policy are not checked here; no complete statutory category count, comparable-scheme appraisal or clear-site conclusion. Failed counts stay unknown and a low river/sea sample never means no flooding. Wales/Scotland use jurisdiction-specific limited routes; other countries return source-registry metadata rather than fetched statutory evidence. Source freshness, full boundary and actual coverage are unverified. Parameter guidance: full address/postcode, radius 250–1000m, optional focus. 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.

Purpose: check planning evidence readiness for a proposal at a resolved England location. When to use: prepare proposal evidence and identify decision references to verify before policy and design appraisal. Returns: bounded national-source sample, explicit source state, dated point-checked decisions from the last five calendar years, supplied proposal and residential density when units/hectares are given. Approval likelihood is always not_estimated, comparable_count and density range are null, and comparability is not assessed. Limitations: incomplete, freshness-unverified national records are not a complete/current local register or a calibrated forecast. No approval percentage, three-approval threshold, inferred scheme density or local-adapter query. Verify relevant approved and refused decisions and current policy on the local authority portal. Parameter guidance: provide address and development_type; optional proposed_units/site_area_ha calculate supplied residential density only, and proposed_height_m is recorded without policy assessment. 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.

Purpose: check a user-supplied red-line boundary before treating it as the site geometry. When to use: run after receiving a GeoJSON Polygon or MultiPolygon, especially before Site Verdict or focused constraint checks. Returns: closure, CRS, coordinate-range, topology, vertex-limit, and area checks; a stable boundary ID; calculated area; visible warnings; and an updated site_ref with red_line_upload confidence only when every blocking check passes. Limitations: V1 accepts EPSG:4326, OGC:CRS84, EPSG:27700, and EPSG:2157; it checks geometry but does not confirm title, ownership, survey accuracy, or a planning conclusion; it does not persist the uploaded geometry. Parameter guidance: pass the GeoJSON Feature or geometry in boundary_geojson, explicitly declare source_crs, optionally provide declared_area_m2 for a mismatch check, and pass an earlier site_ref to retain its address, LPA, and project context. 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.

Purpose: prepare an England permitted-development evidence checklist, tentative class hint and restriction samples, without confirming a legal route. When to use: use for architect questions like "is this rear extension PD?", "can I convert this Class E shop to flats?", or "does Article 4 affect this loft conversion"; use check_planning_constraints when you only need raw constraints. Returns: pd_status always unclear, tentative candidate/applicable class, source states, sample flags, unknown counts and an authority-review checklist. All unresolved restriction evidence returns PD_EVIDENCE_UNAVAILABLE. Limitations: resolved England only; no legal applicability, current-law version, full-boundary intersection, dimensions, original building/use or permission-condition verification. Nearby records and null/small distances never prove containment or removal of a right. Source freshness/completeness are unverified; consult current legislation and the authority. The static keyword matcher is only a proposal hint. Parameter guidance: provide a full address/postcode and a concrete proposal phrase including use, works, and key dimensions where known. 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.

Check first-pass UK planning constraints at a site: flood zone, listed buildings, World Heritage Sites, registered parks and gardens, scheduled monuments, registered battlefields, archaeological priority areas, conservation areas, Article 4 Directions, Tree Preservation Orders, environmental designations (SSSI, AONB, Green Belt, ancient woodland), historic landfill, and ground conditions. UK-only: non-UK addresses return a coverage error. Supply include[] to query specific constraint types only. Returns per-category evidence states, actual query scope, sample flags and gaps. Failed/unreadable results stay unknown; no clear-site opportunity or statutory-completeness claim. Source freshness and full red-line intersections are unverified. All requested categories unresolved returns CONSTRAINT_EVIDENCE_UNAVAILABLE. A regional ground lookup is not a full-radius screen. Use after analyze_site when per-constraint detail is needed. 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.

Read the connected user's active saved Canvas options for one owned development. Use project_id from list_developments. Omit option_ids to choose available options; supply exactly two different IDs to compare immutable captured versions. Recomputes early design quantities from saved geometry and assumptions. No planning verdict, GIA, surveyed area, overlap correction or preferred option. Requires the existing projects permission. Never edits designs. 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.

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

Create an Atlasly project for the resolved site so work can continue inside the full product. Preserves the country and location provenance for plugin reopen. User-supplied coordinates remain unverified with unknown planning jurisdiction; saving does not verify the site, save export files or an evidence snapshot. 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.

Purpose: draft grounded site description, constraints, accessibility, planning history, and policy-context sections for a Design & Access Statement or feasibility note using Atlasly source-backed tool outputs. When to use: use when the user asks for D&A site context, planning statement background, a site description, or a policy-context first draft for a known site; use analyze_site when they only need a concise factual read. Returns: structured sections with headings/body/source_tools, data_gaps, source tool statuses, citations, and next actions. Limitations: this assembles first-draft prose from MCP tool outputs only; it is not a signed planning statement, does not replace specialist reports, and preserves missing data instead of filling gaps with generic claims. Parameter guidance: provide a full address/postcode, development_type, and optional proposed_description with the intended use, height, scale, or works. 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.

Purpose: save enabled Site Watch settings for an owned Atlasly development after the user explicitly requests monitoring. Requires a connected account with atlasly.site_watch.write permission. Inputs: project_id from list_developments, optional checks, weekly/monthly frequency and radius in metres. Replaces that user's existing watch configuration, including previous choices for omitted fields; omitted fields reset to the defaults below. Present the replacement and defaults for user confirmation before calling. Repeating the same settings is idempotent. Planning, flood and competitive checks default to true; web_search defaults to false. The configured monitoring service may subsequently check independently published planning, flood and web sources. Returns saved settings and an Atlasly link only. This call does not perform a source check, verify source coverage, confirm scheduling or promise future alerts. Review completed checks and delivery in Atlasly. Never enable monitoring without the user's explicit request. 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.

Purpose: estimate England planning application fees, CIL coverage/liability status, and likely S106 heads for early feasibility and viability checks. When to use: use when a user asks for planning fees, CIL, S106, planning obligations, or rough pre-application cost exposure; use get_local_plan_policies for policy citations. Returns: planning_fee with calculation basis, unverified CIL schedule/rate/total, typical S106 review heads, caveats, sources, and next actions. Limitations: England-focused narrow fee estimate using the cited April 2026 schedule; outline applications require unavailable site/category inputs and return no fee; CIL schedules and rates remain unverified; it does not replace LPA fee calculators, exact CIL charging schedules, relief checks, indexation, or legal/quantity-surveyor advice. Parameter guidance: provide address, development_type, and either residential_units for housing or gross_floor_area_sqm for non-residential/change-of-use schemes; set application_type when the category is known; no outline estimate is supported. 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.

Purpose: validate and export a supplied WGS84 boundary as GeoJSON or SVG. When to use: when the user provides a Polygon, MultiPolygon or Feature and wants a portable boundary file. Returns: actual file contents, filename, MIME type, geometry checks and limitations; the workspace supports host-mediated download. Limitations: only supplied 2D boundary geometry, no buildings, roads, terrain, constraints or ownership verification; SVG is illustrative and not to scale; reject projected coordinates until reprojected to WGS84. Parameter guidance: pass boundary_geojson, format geojson or svg, and optional title. Do not invent a boundary from an address. 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.

Purpose: retrieve source geometry and prepare a portable site-context file. When to use: when the user wants OpenStreetMap buildings, roads, water, green space and land use worldwide or available UK flood/heritage geometry around a location for QGIS, Rhino or CAD. Returns: actual GeoJSON, SVG or 2D DXF file contents, or a ZIP containing all three from one retrieval, source preview, per-layer coverage, and a companion manifest with CRS, local origin, attribution and limitations. DXF is local WGS84 UTM metres, not longitude/latitude; polygon holes are separate closed polylines. Limitations: community OSM geometry is not a survey; no inferred heights, terrain, DWG, 3D or desktop execution; basemap geometry is generalized and clipped to the request area; other sources retain touching features by default; an optional supplied outline can clip geometry with explicit omissions and an original-source audit companion. England flood checks the address point, not all nearby polygons. Missing layers remain explicit and can produce a partial export. Parameter guidance: supply address including city/country, prior site_ref, or user-supplied coordinates {lat,lng} with country_code. Coordinate mode does not verify the address or planning jurisdiction and only retrieves regional context. Pass a two-letter country code for non-UK address lookup and every supplied point (for example in, us, fr, au), selected layers, format and optional 250–1000m radius/title. Do not treat missing geometry as a clear planning 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.

Purpose: find and rank official English brownfield-register development-site candidates for an area, then enrich the shortlist with Atlasly flood, heritage, conservation-area, and transit checks where requested. When to use: use for site-selection briefs like "find brownfield residential sites in Salford over 0.25ha, outside Flood Zone 2/3, near tram or bus"; use analyze_site for a single known site and check_planning_constraints for raw constraints. Returns: ranked candidates with address, coordinates, score breakdown, brownfield capacity fields, constraint flags, nearest transit where checked, source URLs, and missing-criteria warnings. Limitations: first-pass LPA-boundary search against planning.data.gov.uk brownfield-land only; not a full parcel/ownership/Overture warehouse, does not find off-register sites, and uses published point coordinates before full boundary verification. Scores are heuristics; criteria affect ranking, not guaranteed exclusion. The area application grid uses only checked points from at most 50 incomplete national records within up to 1000m, with failed counts unknown and no probability, inferred use or persistent/local-adapter cache. Freshness and completeness are unverified. Parameter guidance: pass search_area as an English address/postcode/LPA, development_type, optional min_site_area_ha, max_flood_zone such as "Zone 1", transit distance, and exclusion flags for conservation/listed-building proximity. 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.

Purpose: retrieve explicitly decided records from a bounded national planning-application sample for a resolved England site. When to use: to locate application references for manual decision and policy verification. Returns: known approved/refused/withdrawn sample records, source state, nullable dates and location limits; unknown decisions are excluded from precedents. Limitations: records are not verified comparable schemes or an approval forecast; local-register coverage and freshness are incomplete/unverified. No inferred approval from missing status, policy documents, building height, units or use class. Parameter guidance: use an England address or resolved reference, radius 250–1000m, limit 1–10, and proposal_text as a literal filter on returned reference/address/description. 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.

Generate a structured site brief from Atlasly project memory and conversation context. 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.

Purpose: compose multiple Atlasly source-backed site layers into one shareable map URL for feasibility reports, client decks, and planning context review. When to use: use when the user wants a single map with flood, heritage, planning history, transport, constraints, or precedent layers; use get_map_layer_plan when they only need machine-readable layer actions without running source tools. Returns: map_url, encoded map_config, layer_summary, source tool statuses, citation-aware map_layer_plan, data gaps, and sources. Limitations: resolved England only, 250–1000m; this pass composes an encoded request rather than proving rendered geometry. Metadata-planned layers are registrations, not render acceptance. Returned application/place counts are samples, failed counts stay unknown and constraint cards are not feature counts. No separate H3 density fetch or cache write is made. Source coverage, geometry and styling need verification in Atlasly before reuse. Parameter guidance: provide address, optional layers from flood/heritage/planning_history/transport/constraints/precedents, optional radius_meters, and an optional title. 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.

Purpose: retrieve reported flood point evidence with source-state and coverage limits. When to use: first-pass flood evidence before authority/site-specific review. Returns: UK reported zone/native SEPA likelihood and gaps; US native FEMA context if configured. Limitations: no whole-site/access determination, no UK 3a/3b subtype acceptance, no generated risk/FRA/sequential/exception outcome; low river-sea context never means no flooding. Failed UK sources return FLOOD_EVIDENCE_UNAVAILABLE and unknown facts. Source freshness/completeness and current applicability remain unverified; NI/outside coverage use explicit fallback. Parameter guidance: full address or prior resolved site_ref; use local flood authorities for unsupported jurisdictions. 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.

Poll the status of an async Atlasly job (e.g. site package run). Returns current status, progress, and result summary when complete. Poll every 10–30 seconds until status is complete or failed. 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.

Purpose: review stored England local policy extract leads for a resolved authority. When to use: early planning statement research, with source links where available. Returns: a bounded extract sample, unknown adoption/currentness/applicability and a current national framework link. Missing results do not mean no policies; retrieval failure and zero matches are not distinguishable in the existing source helper. Limitations: no template citations, obsolete chapter references, complete council coverage or adopted-plan verification is promised. Check current documents and implementation arrangements before citation. Parameter guidance: provide address and development_type, with optional topic to focus retrieval. 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.

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.

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.

Return structured map actions, source-backed evidence layers, missing layers, citations, coverage status, and warnings for Atlasly site-intelligence map customization requests. This plans layers and draws nothing: use generate_site_map for a rendered map image and open_atlasly_workspace for the interactive map. Supply address or site_ref. 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.

Purpose: find mapped nearby schools, shops and services worldwide. When to use: compare local place context around a known site, or prepare mapped points for QGIS. Returns: selected OpenStreetMap point categories from fixed regional sources, straight-line distances in metres, per-layer coverage, source references, an inspectable map and GeoJSON. Limitations: community mapping, not official access evidence or a complete inventory; source freshness, entrances, opening hours and public/wheelchair access are unverified. No walking routes, travel times, parks, bus stops, rail stations or transit frequency; do not infer a walk score or 15-minute-city verdict. Parameter guidance: supply address with country, a prior site_ref, or WGS84 coordinates {lat,lng} with explicit country_code. Non-UK address lookup requires the configured service. Persona selects default category groups; explicit categories can request only mapped schools, hospitals or other supported point types. Radius is 250 to 1000 metres. Missing data means unknown, never absence of services. 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.