Skip to main content
Glama

Check Planning Constraints

check_planning_constraints
Read-onlyIdempotent

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.

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

Input Schema

NameRequiredDescriptionDefault
addressNoSite address or postcode
includeNo
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.
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.

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
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses failure semantics (unreadable results stay unknown, CONSTRAINT_EVIDENCE_UNAVAILABLE when all unresolved), limits of the claim (no clear-site/statutory-completeness guarantee, freshness and full red-line intersections unverified), and the regional-lookup caveat. This is substantial behavior context annotations cannot convey.

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?

Front-loads the constraint list, then layers caveats and chaining guidance. It is dense and long, and a few caveats are packed into run-on clauses, but each sentence carries operational value for a constraints tool.

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?

With an output schema present and rich annotations, the description fills remaining gaps: scope boundaries, error states, false-negative risks, and chaining via site_ref. An agent has everything needed to call it correctly and interpret the response.

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 75%, so much is already documented, but the description maps the human categories (flood, heritage, conservation, etc.) onto include[] usage and reiterates site_ref chaining semantics that matter for correct invocation. It adds meaning beyond raw field descriptions.

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?

States a specific verb (check) and resource (UK planning constraints at a site) and enumerates the concrete categories covered. An agent can distinguish this constraint screen from siblings like get_flood_risk or prepare_heritage_review, which cover only subsets, without opening the schema.

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?

Gives explicit sequencing ('Use after analyze_site when per-constraint detail is needed') and a hard scope exclusion ('UK-only: non-UK addresses return a coverage error'). It also explains include[] for narrowing scope, though it does not name specific alternative tools like get_flood_risk for a single-category query.

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