Skip to main content
Glama

New build premium

new_build_premium
Read-onlyIdempotent

Use this for how a new home’s asking price compares with resale homes nearby: the premium from HM Land Registry sales adjusted by the house price index, with its range, confidence and the sales it rests on, or why no figure is given (Scotland, too few sales, or no measured method yet). At low confidence there is only a range. Give a home page address.

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": {
      "home": "<home>"
    },
    "name": "new_build_premium"
  }
}

Input Schema

NameRequiredDescriptionDefault
homeYesA home page address from a search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond them by disclosing the return shape (range, confidence, and the sales the figure rests on) and the no-figure cases (Scotland, too few sales, no measured method yet), plus the low-confidence degradation to a range only. It does not cover what happens if the address does not resolve to a home, leaving a small gap.

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?

It is front-loaded with the trigger phrase 'Use this for' and every clause contributes information about inputs, outputs, or failure modes. The middle sentence is dense with parentheticals and slightly run-on, costing it a point.

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?

With one required parameter, no output schema, and read-only annotations, the description supplies everything an agent needs: the metric's origin, the return fields, the confidence behavior, and why a result may be absent. Nothing material is missing for correct invocation.

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% and there is a single documented parameter, so the schema carries the semantics. 'Give a home page address' merely restates the schema's 'A home page address from a search' without clarifying format or resolution behavior, so baseline 3 applies.

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 names a specific computation on a specific resource: how a new home's asking price compares with nearby resale homes, derived from HM Land Registry sales adjusted by the house price index. That is far more precise than the title 'New build premium' and makes the tool unmistakable against sibling calculators and search tools.

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 how a new home's asking price compares with resale homes nearby' establishes the use case clearly, and 'Give a home page address' signals the prerequisite that a home page address from a search is needed first. There are no explicit exclusions or named alternatives, so it stops just short of a 5.

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