MarketCode

Rated commercial stock in an authority

sourcing_commercial

Read-onlyIdempotent

Rated commercial stock in a local authority, filtered by sector and
rateable value — the commercial sourcing lane. Each row carries its
rateable value, an income-basis value, the freeholder where a title links,
and any auction history.

NO £/m² IS PUBLISHED and you should not compute one. The VOA's measured
area is not loaded, and dividing a hereditament-level rateable value by
the twin's unit-level floor area gives nonsense — it produced £235,301/m²
on a Westminster office before it was removed.

`lad_code` is REQUIRED and is the only scope: this is the one indexed way
into the twin for a bounded set of hereditaments. Use `area_resolve` to
turn a place name into a GSS code.

RATEABLE VALUE IS NOT RENT. It is the VOA's estimate of annual rental
value at the rating list's antecedent valuation date (1 April 2024 for the
2026 list). Do not quote it as passing rent or as income.

`income_basis_value` divides that RV by the district's own commercial
auction yield, so it is an arithmetic conversion anchored to local
evidence, not a valuation — and it reads `not_available` where the
district has no auction yield evidence, because a default yield would
produce a number that looks like a valuation. Report the yield and the
number of lots behind it.

One rating list is loaded (2026), so there is no RV trajectory per
property, no measured floor area from the VOA, and no vacancy signal.
UK only. Costs 10 credits (10p).

Input Schema

Name	Required	Description	Default
`limit`	No
`max_rv`	No
`min_rv`	No
`offset`	No
`sectors`	No
`lad_code`	Yes
`scat_codes`	No
`with_owner`	No
`single_hereditament`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes far beyond the readOnly/idempotent annotations: discloses the credit cost (10), UK-only coverage, that only one rating list (2026) is loaded so no RV trajectory or vacancy signal exists, that income_basis_value can return `not_available`, and that £/m² must not be computed. This is exactly the operational context annotations cannot carry.

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 what it returns, then the derived-value caveats; every paragraph is doing work. The 'valued' framing is somewhat repetitive ('NOT RENT' admonition restated in the income_basis paragraph), which costs a point but not much.

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

Completeness4/5

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

An output schema exists so return shape needn't be explained, and the description covers method, limits and cost thoroughly. The remaining gap is pagination and the scat_codes/sectors vocabulary for a 9-parameter tool, which an agent calling it will hit immediately.

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 0%, so the description must compensate. It explains lad_code, RV filtering (min/max), sectors, with_owner (freeholder where a title links) and hereditament granularity, but says nothing about limit, offset or scat_codes, leaving a third of the surface undocumented in both places.

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 ('Rated commercial stock in a local authority') plus its scoping dimensions (sector, rateable value) and explicitly labels itself 'the commercial sourcing lane', which separates it from sourcing_live_listings, sourcing_owners and commercial_property without opening any schema.

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?

Gives one explicit routing rule ('Use `area_resolve` to turn a place name into a GSS code') and states lad_code is required and is the only scope. It does not say when to prefer this over siblings like commercial_property or sourcing_search, so the exclusion half is missing.

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?