MarketCode

One composed document for an area

area_report

Read-onlyIdempotent

The market for one area, as one document: sourcing readiness per strategy
from the coverage register, the commercial capital and rent indices with
rated stock, the planning decision record for the authority, and the live
listing stock.

THE TWO SCOPES ARE NOT INTERCHANGEABLE. Readiness, commercial stock and the
planning register are keyed on the LOCAL AUTHORITY (`lad_code`, a GSS code
— use `area_resolve` to get one); the live listing lane is keyed on
POSTCODE DISTRICT. Pass both to fill every section, and expect the
unsupplied half to read `not_available` with that reason rather than empty.

As with `property_report`, check `sections_degraded` before describing the
document as complete.
UK only. Costs 25 credits (25p).

Input Schema

Name	Required	Default
`sector`	No	ALL
`lad_code`	No
`postcode_district`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely useful context: UK-only scope, a 25-credit cost, and the degradation/`not_available` semantics. It stops short of describing section structure or output shape, but the output schema covers that.

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 one-document purpose, then the critical scope warning in caps, then operational notes. Slightly dense but each sentence carries non-obvious information; the caps warning earns its emphasis.

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?

Covers scopes, keying, degradation behavior, cost, and geography, and an output schema covers return structure. Nothing an agent needs to invoke it correctly is missing.

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?

With 0% schema coverage the description must carry the parameters, and it thoroughly explains `lad_code` (a GSS code, local-authority keyed) and `postcode_district` (live-listing keyed). `sector` (default ALL) is left unexplained, a minor gap against otherwise strong param guidance.

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 and resource: composes a single market document for one area, enumerating its sections (readiness, commercial capital/rent indices, planning record, live listings). It explicitly differentiates from `property_report` and points to `area_resolve` for keying, so an agent can tell it apart from single-lane siblings.

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?

Explicit about the two non-interchangeable scopes (LAD code vs postcode district), tells the agent to pass both to fill every section, and explains what happens when one is omitted (`not_available`). It also directs checking `sections_degraded` and names `area_resolve` as the way to obtain a `lad_code`.

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?