Skip to main content
Glama
UK Business Tools - Ledgerhall

UK Business Tools - Ledgerhall

Prop Ppd Transactions

prop_ppd_transactions
Read-only

Retrieve recent Land Registry Price Paid sales for a UK postcode, optionally filtered by property type, to check comparable transactions within the dataset's coverage.

Instructions

Land Registry Price Paid transactions for a postcode, most recent first.

Returns up to limit most recent transactions within snapshot coverage (coverage_from-coverage_to in the response's provenance). Unfiltered by default -- category-B bulk transfers and commercial sales are included. Pass property_type (F=flat, D=detached, S=semi, T=terraced, O=other) to restrict the result to a single type.

Not a complete property history. Check provenance.older_records_exist and provenance.sample_complete before saying anything about what a property has or has not sold for. An empty result means "no sales within the stated coverage" -- never "never sold". For clean residential comparable sales, use property_comps.

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": {
      "postcode": "<postcode>"
    },
    "name": "prop_ppd_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
postcodeYes
property_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.9/5.0
Behavior5/5

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

Beyond `readOnlyHint: true`, the description discloses non-obvious behavior: results are bounded by snapshot coverage in `provenance`, category-B bulk transfers and commercial sales are included by default, an empty result is scoped rather than absolute, and completeness flags must be checked first. These are exactly the traits an agent could not infer from the annotations.

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 default behavior, then the mapping, then the caveat — a sensible ordering with no filler. The closing caveat is slightly verbose (two sentences on empty-result semantics), which keeps it just short of fully tight.

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?

The tool has an output schema, so return values needn't be spelled out; instead the description points to the specific provenance fields that matter (`coverage_from`/`coverage_to`, `older_records_exist`, `sample_complete`). Nothing an agent needs to call it correctly or interpret the result 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 coverage is 0%, so the description carries the burden and does: `limit` is described as capping the most recent transactions, and `property_type` gets the full code mapping (F=flat, D=detached, S=semi, T=terraced, O=other) that the schema itself does not enumerate. This adds real meaning beyond the input 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 opens with a specific verb and resource ('Land Registry Price Paid transactions for a postcode, most recent first'), and explicitly distinguishes itself from the sibling `property_comps` ('For clean residential comparable sales, use `property_comps`'). An agent can tell exactly what this returns without opening the 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?

It names the alternative tool and the condition that selects it, states the default behavior ('Unfiltered by default'), and explains how to narrow with `property_type`. It also states when *not* to draw conclusions from the result ('never "never sold"'), which is actionable guidance, not just caution.

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

Deploy Server

Other Tools