Axiom Works AgentReader

uk_property_prices

Use this for England & Wales house prices near a UK postcode: HM Land Registry Price Paid sales (address, price, date, type, tenure) within radius metres, plus medians. OGL. $0.01 USDC. Related: Area profile: /uk-area $0.005.

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": "uk_property_prices"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`radius`	No
`postcode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the burden and discloses the data source (HM Land Registry Price Paid), the OGL licensing, and a per-call cost of $0.01 USDC — all real behavioral context. It does not mention data-lag/coverage caveats or failure behavior for bad postcodes, so it is strong but not complete.

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 'Use this for', and every clause carries information: scope, source, returned fields, license, price, related tool. The telegraphic 'OGL. $0.01 USDC.' fragments are efficient rather than wasteful, though the trailing related-tool note reads slightly like an advertisement.

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?

No output schema exists, and the description compensates by listing the returned fields and medians. Combined with source, license, and cost, an agent has enough to call it correctly; only limit semantics and postcode format remain gaps.

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 does give the unit meaning for radius ('within radius metres'), which the schema lacks. However, it never explains limit (typed as a string, purpose ambiguous) or the expected postcode format, leaving two of three parameters opaque.

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 and scope: HM Land Registry Price Paid house price sales near a UK postcode in England & Wales, including the returned fields (address, price, date, type, tenure) and medians. It also names the adjacent uk_area_profile tool, so an agent can separate it from the closest sibling.

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?

'Use this for England & Wales house prices near a UK postcode' gives a clear positive trigger and geographic boundary. It points at the related /uk-area profile, but only as an upsell, without stating the condition under which the agent should pick that instead, and it gives no exclusions.

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

All Axiom Works AgentReader 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.