Draft Site Description
draft_site_descriptionPurpose: 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.
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": {
"development_type": "<development_type>"
},
"name": "draft_site_description"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| address | No | Site address or postcode for the grounded draft | |
| site_ref | No | Canonical 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. | |
| development_type | Yes | Development category, e.g. residential, mixed-use, commercial, extension, change of use | |
| proposed_description | No | Optional proposal description, e.g. six-storey residential block with ground-floor commercial |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | ||
| status | Yes | ||
| details | No | ||
| message | No | ||
| sources | Yes | ||
| headline | Yes | ||
| site_ref | Yes | ||
| retryable | No | ||
| error_code | No | ||
| atlasly_link | Yes | ||
| error_source | No | ||
| human_message | No | ||
| key_data_points | Yes | ||
| top_constraints | Yes | ||
| confidence_notes | Yes | ||
| executive_summary | Yes | ||
| next_best_actions | Yes | ||
| top_opportunities | Yes |