Skip to main content
Glama
Sign In

Listing Location Toolkit

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Home buyer report for an address

home_buyer_report
Read-onlyIdempotent

Everything a home buyer asks about one address, in one call: nearby primary, middle, secondary and private schools (England: Ofsted grades or report cards, pupils, faith, selective; US: grades, pupils per teacher, free lunch share, and the school district the address is in), how admissions and catchments work there, everyday places (supermarket, doctor, pharmacy, dentist, station, bus stop, park, playground, library, gym, cafe, pub, EV charger) with walk and drive minutes, a 15 minute walk check, the neighbourhood (US census tract income, home value, rent, owners, households with children, commute, against county and US; England deprivation deciles; England and Wales sale prices by property type for the postcode sector), flood zone (FEMA in the US, Environment Agency in England) and street crime for the latest month (England, Wales and Northern Ireland). Returns listing_lines, the raw data and sources. Takes 10 to 25 seconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "home_buyer_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude in decimal degrees (use with lon instead of address).
lonNoLongitude in decimal degrees.
addressNoStreet address with town and ZIP or postcode, e.g. "7090 State Highway 80, Cooperstown, NY 13326" or "Ambleside LA22 9BB". Not needed when lat and lon are given.
countryNoOptional hint for the address lookup.
includeNoParts to include. Default all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive, so the bar is lower, and the description still adds real value: a 10–25 second latency expectation, region-specific data availability (crime only England/Wales/Northern Ireland, FEMA vs Environment Agency flood, US census tract vs England deprivation), and the fact that raw data plus sources come back. It does not explain failure behavior for unsupported geography (e.g. crime in the US) or rate limits.

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 lead clause is well front-loaded, but the body is one very long run-on sentence with dense parenthetical enumerations that are hard to scan. Most content earns its place, yet the packing into a single sentence hurts structure.

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?

For a 5-parameter, no-output-schema tool, the description covers what data comes back per region and names the return keys (listing_lines, raw data, sources). The return shape could be described slightly more, but the geographic coverage and latency disclosures make it largely sufficient.

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 address, lat/lon, country and the include enum are already documented in structured data — baseline 3. The description never mentions parameters directly, though its content categories map onto the include enum values, giving only indirect support.

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 and resource — a single-call report on one address — then enumerates its contents by category (schools, daily needs, area, flood, crime) with concrete data points. An agent can distinguish it from the narrower siblings (schools_nearby, crime_nearby, flood_risk) without opening a schema.

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?

"Everything a home buyer asks about one address, in one call" clearly signals this is the aggregate alternative to the single-topic siblings, and the 10–25 second note sets a cost tradeoff. It stops short of explicitly saying "use this instead of calling schools_nearby and crime_nearby separately" or when a single-topic sibling is preferable.

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

All Listing Location Toolkit toolsInspect
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.

Resources