Skip to main content
Glama

BRAINIAC Official Property & Energy Lookups

Look up UK House Price Index figures

property-official_uk-hpi-lookup
Read-onlyIdempotent

Return official UK HPI average price, index and change figures for a geography and month from the vendored HM Land Registry full file. Price $0.03 USDC. POST /api/v1/property-official/uk-hpi-lookup. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "area": "<area>"
    },
    "name": "property-official_uk-hpi-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoto, string. Optional.
areaYesarea, string, length 1 to 200. Required.
fromNofrom, string. Optional.
monthNomonth, string. Optional.

Output Schema

NameRequiredDescriptionDefault
areaNoarea. Object.
seriesNoseries. Array.
releaseNorelease. String.
sourcesNosources. Array.
limitationsNolimitations. Array.
publishedAtNopublishedAt. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds critical invocation context beyond that: cost ($0.03 USDC), the unpaid x402 payment flow, and the fact that an unpaid call does not execute.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose, then compactly covers cost, endpoint, and payment behavior. Every sentence carries useful information and there is no redundant restatement of annotations.

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 and annotations cover safety and idempotency, so the description need not explain return values. It adds source and payment behavior, but leaves gaps around area values and the semantics of month versus from/to ranges.

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 description coverage is 100%, so the schema documents all four parameters. The description only says 'geography and month' and does not explain area formatting or the relationship between month and the optional from/to range parameters, so it adds little beyond the 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?

The description uses a specific verb ('Return'), names the exact dataset (official UK HPI), lists the figures returned (average price, index, change), and identifies the source (vendored HM Land Registry full file). An agent can distinguish this from the other official-property lookup siblings by dataset.

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?

It implies usage for UK HPI lookups by geography and month, but gives no explicit when-to-use guidance, no alternatives, and no guidance on choosing between month and from/to ranges.

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