Skip to main content
Glama

New home details

get_home
Read-onlyIdempotent

Use this for the facts of 1 to 6 homes, side by side when more than one: price and its history since first listed, status, rooms, floor area, tenure and lease, service charge and ground rent, council tax band, EPC, parking, expected completion, key features, every offer the builder states, the cash needed to complete, the other plots of the same house type with their prices and those that sold or left, and the area around it. Name homes by the page address a search returned. A fact the builder does not state comes back as not stated.

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": {
      "homes": "<homes>"
    },
    "name": "get_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
homesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that — 'A fact the builder does not state comes back as not stated' — plus the side-by-side multi-home response shape. It says nothing about ref resolution failures, partial results, or cost/latency of batching up to six homes.

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

Conciseness3/5

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

The usage directive and the ref-naming rule are front-loaded, which is good, but the middle is a single ~60-word run-on enumeration of roughly seventeen fact categories. The list earns its place in lieu of an output schema, yet it is unstructured and would read far better as grouped clauses or a short bulleted set.

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?

There is no output schema, so the description is the only source for return values, and it discharges that well by naming the fields and the 'not stated' placeholder. Gaps remain around error behavior for bad refs and whether all six homes must resolve before anything is returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero schema description coverage on the top-level parameter, the description carries the load and does so: it fixes cardinality (1 to 6 homes) and explains the accepted identifier form ('the page address a search returned'), matching the item-level ref-or-URL pattern. It does not spell out what happens with a malformed or unknown ref.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb+resource ('the facts of 1 to 6 homes') and enumerates the exact fact set returned (price history, tenure, service charge, EPC, offers, cash to complete, comparable plots, area). It points back to 'the page address a search returned', which implicitly separates it from the search tools. It stops short of naming a sibling outright, so an agent must infer that search_homes is the discovery counterpart.

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?

It gives a clear usage condition — 'Use this for the facts of 1 to 6 homes, side by side when more than one' — and a prerequisite: homes must be named by a reference a search already returned. No explicit when-not clause or named alternative is given, so the exclusion side is left implicit.

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