real-estate-data-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_housing_statsA | Get housing statistics for a US state or county. Returns median home value, median rent, vacancy rates, and owner-occupied percentage from the US Census ACS 5-Year survey. Args: state: US state name or abbreviation (e.g., "California" or "CA") county: Optional 3-digit FIPS county code (e.g., "073" for San Diego) |
| get_area_demographicsA | Get demographic data for a US state or county. Returns population, median income, education levels, employment stats, and age distribution from the US Census ACS. Args: state: US state name or abbreviation (e.g., "Texas" or "TX") county: Optional 3-digit FIPS county code (e.g., "201" for Harris County) |
| get_nearby_amenitiesA | Find nearby amenities around a location using OpenStreetMap. Returns schools, hospitals, parks, transit stops, supermarkets, restaurants, and pharmacies within the specified radius. Args: lat: Latitude of the location lon: Longitude of the location radius_m: Search radius in meters (default: 2000, max: 5000) |
| compare_areasA | Compare housing metrics for multiple US areas side-by-side. Compares median home value, rent, income, population, and affordability for 2-5 different locations. Args: locations: List of location dicts, each with 'state' (required) and optional 'county' FIPS code. Example: [{"state": "CA"}, {"state": "TX", "county": "201"}] |
| get_cost_of_livingB | Get housing affordability and cost-of-living indicators for a US state. Returns housing costs relative to income, affordability index, housing burden analysis, and cost comparisons. Args: state: US state name or abbreviation (e.g., "New York" or "NY") |
| search_neighborhoodsA | Search for neighborhoods/areas in a city with key housing stats. Geocodes the city, finds the state, then returns all counties and places in that state with housing and demographic data. Args: city: City name with state (e.g., "Austin, Texas" or "Miami, FL") |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Tools like get_housing_stats, get_cost_of_living, and get_area_demographics overlap in scope but are distinguished by their specific focus on raw housing data, affordability indices, and demographics, respectively. The descriptions clarify these differences, though potential confusion remains between similar state-level data retrieval tools.
All tools follow a consistent verb_noun pattern using underscores (e.g., get_area_demographics, compare_areas), with 'get' as the common action verb. No mixing of casing or verb styles is observed.
6 tools is an appropriate scope for a real estate data server, covering key area-level statistics, comparisons, and nearby amenities without being excessive or sparse. Each tool has a distinct role.
The tool set covers essential area-level housing, demographic, and cost-of-living data, plus neighborhood search and amenities. Minor gaps include the absence of zip-code-level data and property-specific listings, but these are within the stated domain focus.