That is a different answer from a price index, and it is the one an offer actually turns on — the same floor area at a different orientation or a different floor is a different number. get_community_rating and get_community_valuation sit around it to supply the context a single valuation lacks: how the community scores on management, education and district, and where its average price has run between start_time and end_time. Every call is keyed on city, district and community_name, so a question has to name a community before this server can answer it.
A residential property valuation service keyed on the named community: ratings for the community, its average price over a time window, and a valuation for an individual home inside it.
- A valuation for one specific home: get_property_valuation takes orientation, floor_area, located_floor and total_floors alongside city, district and community_name, and returns an estimated total price together with an estimated unit price.
- How the community itself scores: get_community_rating returns the community rating, the activity rating, the property-management rating, the education rating and the district rating for a community_name within a city and district.
- Where the community's prices have been: get_community_valuation returns average price information for a community across the window set by start_time and end_time.
An application id, supplied as MCP-INDUSTRY-APPID.
One command — npx -y mcp-property-valuation-server@0.0.27