MarketCode

Chosen planning designation checks

planning_check

Read-onlyIdempotent

The planning designation checks you choose, for one location, in one
call. `checks` is any of: article_4, brownfield, ancient_woodland,
heritage_at_risk, tpo, aqma, scheduled_monument, sssi, agricultural_land,
flood_risk, green_belt, listed_buildings, aonb, national_park,
conservation_area — omit it for all fifteen. Each check reports its own
result, and one that could not be read says `status: unknown` rather
than disappearing. Use `planning_designations` for the fixed bundle of
thirteen; use this when you need SSSI or agricultural land grade, or only
two or three checks. Give either `postcode` or `location` as "lat,lng".
UK only. Free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`checks`	No
`location`	No
`postcode`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive. The description adds genuine behavioral context beyond them: a failed check reports `status: unknown` rather than disappearing, omitting `checks` returns all fifteen, and it's UK-only and free. Solid added value though not exhaustive.

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-loaded with the core purpose, then the enum list and alternative routing. The long enumeration is necessary but makes it slightly dense; every sentence still earns its place.

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 (return values needn't be described) and annotations covering the safety profile, the description supplies everything else: valid inputs, defaults, error behavior, region, and sibling routing. Nothing an agent needs is missing.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load, and it does: it enumerates all fifteen valid `checks` values, specifies the omit-for-all default, gives the "lat,lng" format for `location`, and states 'give either postcode or location'. This fully compensates for the bare schema.

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 (checks) and resource (planning designations for a location), and explicitly names and contrasts the sibling planning_designations. An agent can distinguish it from the sibling without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes usage: 'Use planning_designations for the fixed bundle of thirteen; use this when you need SSSI or agricultural land grade, or only two or three checks.' Both the when and the alternative are spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MarketCode tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?