Skip to main content
Glama

Commercial rent index

commercial_rent_index_series
Read-onlyIdempotent
Commercial RENT index from the VOA rating lists — FOUR points, one per
list (2010 / 2017 / 2023 / 2026), each dated at that list's antecedent
valuation date (2008-04-01, 2015-04-01, 2021-04-01, 2024-04-01), with the
2010 list = 100.

READ `basis` AND REPEAT IT when you quote a number: the index is derived
from VOA rateable values — the Valuation Office Agency's assessment of
open-market rent at each valuation date — NOT from advertised rents, and
it is not a capital-value index. It moves in four steps; do not
interpolate between them as if it were monthly, and date each point by
`avd_date`, not `list_year`.

Why it exists: it covers the sectors the repeat-sales capital index
cannot (INDUSTRIAL_WAREHOUSE trades in portfolios, not Price Paid), for
every VOA sector and 320 local authorities.

`sector`: omit for ALL, or a VOA sector (OFFICE, RETAIL,
INDUSTRIAL_WAREHOUSE, INDUSTRIAL_FACTORY, PUB_BAR, HOTEL, LEISURE,
HEALTHCARE, EDUCATION, ...). `area`: omit for national; a local
authority GSS code ("E08000003") or NAME ("Manchester", bridged to its
code). `start` / `end`: rating-list years, e.g. "2017".

`link_ratio` is the median rateable-value ratio between consecutive lists
over the hereditaments present in both (`n_constant` of them). An empty
`series` with `available_sectors` means the area is published but not
that sector; an unknown area is an error. UK only. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNo
areaNo
startNo
sectorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already carry the safe-read profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds material behavior: the index derives from VOA rateable values, not advertised rents or capital values; it moves in four discrete steps; points must be dated by `avd_date` not `list_year`; and it defines error/empty semantics (unknown area is an error, empty `series` with `available_sectors` means the sector is unpublished). That is well beyond the structured fields.

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 subject (rent index, four points, base year) and then sequences provenance, usage, and per-parameter notes efficiently. It is dense and slightly over-emphatic (all-caps warnings, a repeated 'NOT from advertised rents'), but nearly every sentence earns its place for a tool with a non-obvious index construction.

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?

Given four optional parameters, an output schema (so return shape needn't be explained), and the closed-world read-only annotations, the description supplies everything an agent needs: scope, granularity, date semantics, provenance caveats, and empty/error handling. Nothing material 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% and there are no enums, so the description carries the full burden — and it does: `sector` (omit for ALL or a named VOA sector with examples), `area` (omit for national, GSS code 'E08000003' or name 'Manchester' bridged to code), and `start`/`end` (rating-list years, e.g. '2017'). It also adds value beyond the schema for `link_ratio`/`n_constant` output semantics.

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+resource: a commercial RENT index built from VOA rating lists, with exactly four points tied to list antecedent valuation dates and a 2010=100 base. This is sharply distinguished from the advertised-rent and capital-value siblings (asking_rent_index_series, commercial_index_series) without needing to open 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 strong context for when to reach for it: it covers sectors the repeat-sales capital index cannot (INDUSTRIAL_WAREHOUSE portfolio trades), spans all VOA sectors and 320 local authorities, and is 'UK only. Free.' It warns against monthly interpolation and against quoting without `basis`, but never names a specific alternative sibling to use instead, so it stops short of explicit alternatives/exclusions.

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