PlanWire — UK Planning Data

Agent readability score

Strengths

• Tool names clearly indicate their primary function (e.g., 'search_planning_applications').
• Descriptions include practical use cases (e.g., 'refused extensions in OX1').

Weaknesses

• The 'get_planning_application' tool's description is overly brief, lacking context on its utility.
• No explicit mention of error handling or parameter constraints in any tool descriptions.

• get_planning_application — Description lacks context for when this tool is useful beyond fetching by ID.
• search_planning_applications — Parameter constraints (e.g., required fields) are not explicitly defined.

Verdict

PlanWire's tools are logically distinct and well-named, but the absence of detailed parameter definitions and error handling documentation may hinder agent reliability in edge cases.

9/11/2026, 8:05:11 AM

Event narrative

Server transitioned to legacy era with full compliance score of 100.

Risk: medium

• 2026-09-10T21:16:35.016Z — era changed from auth-gated to legacy · transition may affect user access controls
• 2026-09-11T07:35:54.413Z — complianceScore set from null to 100 · indicates full regulatory compliance achieved

Advice

Monitor compliance score trends and verify legacy era configuration aligns with service requirements. Confirm smokeOk status resolution is not required for current operations.