Skip to main content
Glama

Get Planning History

get_planning_history
Read-onlyIdempotent

Purpose: retrieve a bounded national planning-application sample for a resolved England site. When to use: for first-pass record research with direct local-portal verification. Returns: references, source decision text, known/unknown outcomes, nullable dates, source-point proximity, source state and coverage limits. Limitations: not a current complete local register; national data origin, council coverage and freshness remain unverified. Failed sources return unknown counts, not zero; other jurisdictions require their local registers. No implied approval or absence of applications. Parameter guidance: use an England address or resolved reference, radius 250–1000m, limit 1–20, and optional outcome filter; filtering applies to the returned bounded sample. 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": "get_planning_history"
  }
}

Input Schema

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

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.3/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world safety, yet the description goes further by disclosing unverified national origin, council coverage and freshness, and the critical caveat that failed sources return unknown counts rather than zero. It also warns against reading absence of records as absence of approvals — exactly the fail-mode an agent would otherwise get wrong.

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?

Labeled sections (Purpose/When to use/Returns/Limitations/Parameter guidance/Chaining) make it scannable and front-load the core purpose. Slight redundancy — 'bounded' and 'national' recur across four sentences — but no filler sentences.

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?

For a 5-parameter, open-world research tool with an output schema, nothing an agent needs to call it correctly is missing: input bands, sample-vs-population caveat, jurisdiction exclusion, and the site_ref chaining contract are all covered.

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?

At 60% schema coverage the description carries real weight: it states the accepted radius band (250–1000 m), limit range (1–20), and that the outcome filter applies only to the already-bounded sample, which the schema does not say. The site_ref pass-through instruction is also made explicit, though it partly duplicates the schema's own description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('retrieve a bounded national planning-application sample') with geographic scope ('resolved England site'), which separates it from local-register lookups. It stops short of naming a sibling tool, but the scope boundary is unambiguous.

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?

'When to use: for first-pass record research with direct local-portal verification' gives a clear trigger and an accompanying condition. The Limitations block adds an explicit exclusion ('other jurisdictions require their local registers'), though no sibling Atlasly tool is named as an alternative.

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