Skip to main content
Glama

Plan Site Intelligence

plan_site_intelligence
Read-onlyIdempotent

Resolve a site into a structured data-source route: which Atlas warehouse datasets apply, which official sources are verified for this jurisdiction, which categories have coverage gaps, and what research fallback applies for uncovered categories. Use before making planning analysis claims to understand which data sources and datasets are available for the site's jurisdiction. Returns warehouse_lookup_plan, verified_sources, missing_categories, and confidence. Does not fetch live constraint data: use per-constraint tools such as get_flood_risk, check_planning_constraints or prepare_heritage_review for that. 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.

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": "plan_site_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoSite address or postcode
questionNoThe site-analysis question to route
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.
categoriesNoOptional requested domains such as planning, flood, heritage, ecology, transport, terrain, climate
radius_metersNoSearch radius in metres around the site. Requests above the caller's limit (1,000 m without an account, 2,000 m with one) are reduced or rejected.
include_candidatesNoInclude unverified candidates as labelled background context in route diagnostics

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. Changed1 schema field changed
    • addedInput schema / properties / radius_meters / description
      Added value: +"Search radius in metres around the site. Requests above the caller's limit (1,000 m without an account, 2,000 m with one) are reduced or rejected."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and openWorld, so the description correctly focuses on behavior beyond them: that this is a routing/planning call rather than a live-data fetch, what the response returns, and the site_ref chaining convention that lets downstream tools reuse coordinates, LPA, and project context. It does not mention rate limits or permissions, but the radius-limit caveat is already carried by the schema.

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?

Four sentences, front-loaded with purpose, then output fields, then exclusions, then the chaining note — every block earns its place. Slightly dense with enumerated field names that partly duplicate the output schema, keeping it just short of a 5.

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 exists and the annotations carry the safety profile, the description is complete: it names the routing outputs, states the boundary versus live-constraint tools, tells the agent how to supply a site, and documents the site_ref chaining contract that governs correct multi-tool use.

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 the baseline is 3; the description adds value by stating that either address or site_ref supplies the site, and by explaining that site_ref is a canonical object to be passed back unchanged for chaining. It does not elaborate on categories, radius_meters, or include_candidates, but those are documented in 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 ('Resolve a site into a structured data-source route') and immediately enumerates what the route contains: warehouse datasets, verified sources, coverage gaps, and fallback. An agent can distinguish this routing tool from the analysis/constraint siblings without opening any 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?

States explicit timing ('Use before making planning analysis claims') plus a clear exclusion ('Does not fetch live constraint data') naming three concrete alternatives (get_flood_risk, check_planning_constraints, prepare_heritage_review). It also specifies input mode ('Supply address or site_ref') and the chaining contract.

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