Atlasly MCP Tools: Public Discovery and Site-Research Limits

Initialize the MCP connection, then request tools/list. Initialization is not the tool manifest. Use each returned inputSchema to find required fields, permitted values and limits; do not guess a radius or copy a partial JSON fragment from an older article.

The current source adds an optional site_ref to many tools so a returned site reference can carry location context into the next check. Preserve that reference where returned, inspect its boundary confidence, and avoid conflicting address or coordinate overrides. A resolved address point is not a surveyed ownership boundary.

Purpose	Names returned by public discovery
Discovery and source readiness	search_tools; get_lpa_adapter_status; get_official_source_adapters
Site screening and comparison	site_verdict; compare_sites; boundary_doctor; analyze_site; find_development_sites
Planning research	check_planning_constraints; check_permitted_development; get_local_plan_policies; get_planning_history; find_precedents; assess_planning_approval_likelihood
Environmental and heritage research	get_flood_risk; calculate_biodiversity_net_gain; run_sequential_test; get_heritage_impact_table
Costs and regulatory scoping	estimate_planning_costs; check_building_regulations_triggers
Briefing, maps and research support	draft_site_description; generate_site_map; search_aec_knowledge; plan_site_intelligence; get_map_layer_plan
Terrain and movement	get_site_topography; check_walkability_transport

This is the observed public list, not a promise that the list will remain unchanged or that all advertised operations have passed a live result check.

Read the returned status, errors, warnings, source links and coverage notes as well as any summary. Keep the requested location and study boundary with the result. A missing dataset or failed upstream request must remain unknown, rather than becoming evidence that a constraint is absent.

The get_site_topography implementation retrieves point elevation; it does not supply surveyed contours, slope profiles or a full terrain model. Planning likelihood, biodiversity estimates, permitted-development checks and sequential-test support are screening aids. Their names do not establish a planning decision, statutory metric assessment, lawful-development certificate or professional sign-off.

Many relevant public datasets are England-specific. Confirm the applicable nation, authority, policy edition and source for each check. The methodology and limits guide explains the next level of verification.

Source defines five additional operations behind account permissions:

• create_project_from_site saves a project.
• run_site_package starts an account-linked analysis job.
• get_job_status reads a job’s status.
• generate_site_brief creates a project brief.
• enable_site_watch configures recurring site checks.

These were absent from the unauthenticated tools/list response. Their current authorized discovery, account allowances and end-to-end behavior remain unverified in this review. Do not assume that calling a missing name automatically signs a user in. Authorize through the client flow, discover again, and inspect the schema before requesting an action. Do not repeat a write after a timeout without checking whether it already succeeded.

For an illustrative England feasibility review, first establish the site boundary and authority. Inspect source readiness, then select the available planning, flood, heritage and transport checks that answer the brief. Keep each material result beside its primary-source reference and record unavailable evidence.

Only compare two sites after confirming comparable study areas and source coverage. Resolve findings that could change the brief through current official data and the appropriate specialist. This proposed sequence is not a tested claim that every listed operation returns complete evidence for every site.

The reviewed session negotiated MCP protocol 2025-03-26. Protocol negotiation does not freeze Atlasly’s tool catalog or validate every client. Re-discover after reconnecting or receiving a tool-list change notice, and use the current schema.

Source contains tool-call logging that can include site addresses and coordinates. This article does not promise anonymous telemetry, no personal data, or a 30-day retention period. Review actual client disclosures and terms before sending sensitive material.

The public REST hostname previously used in examples did not resolve during the same review. See developer documentation for its publication status; a reachable MCP endpoint does not verify a separate REST API.