Skip to main content
Glama

UK Data: UK trade, property and planning

planning_search

Read-onlyIdempotent

Search planning applications across UK councils by keyword, postcode or authority (PlanIt). (cost: 2 credits)

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

Input Schema

NameRequiredDescriptionDefault
limitNonumber 1-200
queryNostring
daysBackNonumber
postcodeNostring
radiusKmNonumber, with postcode, default 2
authorityNostring

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds genuinely new context beyond that: the underlying data source (PlanIt) and the per-call cost of 2 credits, which matters for an agent budgeting calls. It stops short of describing result volume, pagination, or what an empty result means.

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?

One front-loaded sentence carries the action, scope, source and cost with no filler. The cost parenthetical is useful rather than padding, though the description could spend one more clause on search-mode behaviour without becoming bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero required parameters and six optional ones, the agent does not know what happens if it supplies nothing, how daysBack interacts with a keyword query, or roughly what a result record contains (there is no output schema). The tool is simple enough that this is survivable, but the description leaves real gaps for a broad-search endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 only implicitly maps three of the six parameters (query, postcode, authority) and says nothing about limit, daysBack, or radiusKm, whose schema descriptions are bare types ('number') rather than real explanations; the 'default 2' hint for radiusKm is not echoed or clarified.

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?

The description gives a specific verb and resource ('Search planning applications across UK councils') plus the three lookup dimensions (keyword, postcode, authority) and the upstream source (PlanIt). The domain is unique among the siblings, so an agent can rule out every other *_search tool without opening a schema, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the alternative input modes (keyword vs postcode+radius vs authority) hint at when each is appropriate, but there is no explicit when-to-use, when-not-to-use, or fallback guidance. Nothing tells the agent what to do if a location is outside the UK or which mode to prefer when several are valid.

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