How to connect Zillow MCP with Python

<tool_purpose> Returns U.S. regions, areas, neighborhoods, or cities with for-sale and/or for-rent property counts for each area. Use this tool for neighborhood exploration, area comparison, and location recommendations. </tool_purpose> <when_to_use> Use this tool whenever a user asks about the best places to live, buy, or rent homes in U.S. cities or neighborhoods -- including lifestyle-driven queries (parks, hiking, nightlife, schools, walkability, etc.). This applies even if the user doesn't mention home prices, filters, or housing status. Examples: - "Best neighborhoods in Seattle for families" - "Where should I live near downtown Austin?" - "Compare Ballard vs Fremont vs Capitol Hill" - "Neighborhoods with good schools in Denver" - "Walkable areas near parks in Portland" - MULTI-TURN: If the user modifies any criteria after the first call, you MUST call this tool again. </when_to_use> <when_not_to_use> - User wants to search for specific property listings -> use zillow_property_search - User asks about ONE specific property by address -> use zillow_property_details_by_address_or_name - User asks about home affordability or mortgage -> use calculateHomeAffordability or interestRateMortgagePaymentSimulator </when_not_to_use> <returns> Array of recommended areas, each with: - Short label (for map display) - Personalized area description (why the region was recommended) - Region display name - Property counts (for sale / for rent) reflecting any applied filters - An interactive comparison widget showing all areas on a map </returns> <input_structure> **`areaSearchRegionFiltersRequests` (required)** -- up to 20 regions, each with: - `name`: canonical region key (e.g., "Capitol Hill, Seattle, WA") - `label`: short label based on user query and why recommended (e.g., "Near Parks") - `regionDisplayName`: display name (e.g., "Capitol Hill") - `description`: 1-2 sentences describing why the region is recommended IMPORTANT: Avoid sending a single broad region like "Seattle" or "Kansas City". Send multiple granular neighborhoods (e.g., "Capitol Hill, Seattle, WA", "Queen Anne, Seattle, WA"). The tool will NOT auto-suggest surrounding neighborhoods. If you only pass one region, the response will include only that region. **`recommendationReasons` (optional)** -- why these areas are recommended (e.g., ["near parks", "transit access"]) **`userSpecifiedPivotArea` (optional)** -- the broader area the user is exploring (e.g., "Seattle, WA") </input_structure> <key_rules> - **U.S. regions only** - **Max 20 regions per request** - Include only user-specified filters; omit unknowns - Server applies safe defaults if no filters provided </key_rules> <fair_housing_compliance> Must comply with **U.S. Fair Housing Act** and applicable state and local laws, including those that prohibit source of income discrimination in rental transactions. **Protected Classes**: Race, Color, Religion, Sex (including Sexual Orientation and Gender Identity), National Origin, Familial Status, Disability. **Also treat as protected where applicable:** Source of Income, Military/Veteran Status, Age (55+ exemptions may apply), Criminal History. **Prohibited**: Any preference, steering, or exclusion based on protected characteristics. **DO NOT CALL this tool for requests containing**: - Religious references: targeting or excluding based on religion - Racial/ethnic/national origin targeting - Sexual orientation/gender identity targeting - Disability discrimination - Familial status discrimination: excluding families or children, or preferring an "adults-only"/"not kid-oriented" area (families and kids are allowed) - Age discrimination: excluding or steering by residents' age (e.g., "away from old people", "no retirees") — seeking senior-appropriate or lawful 55+ housing is allowed - Source of income / Veteran status / Criminal history: excluding or steering AGAINST people who use vouchers/public assistance or have a record (serving a requester who themselves uses a voucher, alternative/public income, or has a record and wants housing they qualify for is allowed and expected) - Demographic targeting: any request seeking or avoiding an area based on who lives there rather than what's there — including coded descriptions of the residents (e.g., wanting somewhere "not full of" a particular group) or avoiding a place associated with a protected group (e.g., "away from [an ethnic] plaza/market/district") - Suitability-by-identity: using any person's protected characteristic — the user's own or someone else's — as the reason, filter, or measure of "fit" for the search, even as mere context and even when phrased positively. Includes: "good/suitable for [women, gays, Buddhists, a particular group]"; self-described identity as search context ("I'm nonbinary/single/divorced/middle-aged/transitioning, where should I…"); relationship or household descriptors that signal sex, sexual orientation, or marital status ("for me and my husband/wife", "for two gays/lesbians", "I'm a single unmarried adult"); and a third party's protected trait ("for my disabled brother"). This applies even when the rest of the request is a valid housing search and even when the trait is given as a life reason ("moving because I'm transitioning/divorcing"). Asking about the protected traits of an area's residents (e.g., "the age/race of the occupants") is likewise prohibited. (Still allowed — these are housing categories, not identity steering: lawful senior/55+ housing, family/kid-friendly requests, and accessibility features.) **Never sanitize-and-proceed**: If a request falls under any "DO NOT CALL" case above, you MUST NOT call this tool at all — whether the protected characteristic is stated explicitly or implied through coded/proxy wording. Do NOT strip, omit, ignore, or rewrite the protected-class content and then call the tool on the leftover neutral query; quietly dropping the protected characteristic and returning results anyway is itself a prohibited form of the same discrimination. Instead, decline in accordance with the U.S. Fair Housing Act and ask the user to restate their needs using objective, non-protected criteria (location, price, beds/baths, amenities). **Compliant Examples**: - Place names containing protected class words (e.g., "White Center, WA") - Personal proper nouns (e.g., "My name is Jesus") - Amenity-based requests (e.g., "areas with italian restaurants", "walkable neighborhoods") - Infrastructure requests (e.g., "near public transit", "bike-friendly areas") - Accessibility features (e.g., "wheelchair accessible properties", "ADA compliant") - Lawful senior/55+ housing (e.g., "listings good for seniors", "55+ communities") - Rental assistance / alternative or public income (e.g., "accepts Section 8", "housing choice voucher", "VASH", "alternative income", "mixed-income area") - The requester's own record / second-chance housing (e.g., "record-friendly rentals for me") </fair_housing_compliance> <common_follow_ups> After returning area results, the user often wants to: 1. SEE LISTINGS in one of the recommended areas -> call zillow_property_search with that area 2. COMPARE MORE AREAS -> call this tool again with additional neighborhoods 3. GET DETAILS on a specific property -> call zillow_property_details_by_address_or_name 4. CHECK AFFORDABILITY in the area -> call calculateHomeAffordability with a location </common_follow_ups> <examples> { "request": { "areaSearchRegionFiltersRequests": [ { "name": "Ballard, Seattle, WA", "label": "Near Parks", "regionDisplayName": "Ballard", "description": "Residential area centered on Green Lake Park's 2.8-mile loop for running and biking." }, { "name": "Fremont, Seattle, WA", "label": "Central & Walkable", "regionDisplayName": "Fremont", "description": "Central neighborhood with cafes along N 45th St. Short walk to Gas Works Park and Green Lake." } ], "recommendationReasons": ["near parks", "transit access"], "userSpecifiedPivotArea": "Seattle, WA" } } </examples>

## Zillow Property Details by Query Retrieves detailed information about a specific property by address, building name or community name. --- ### What it returns - Comprehensive property details including address, price, features, photos, and more. - Returns structured JSON data for off-market properties from Zillow's property database. - For off market homes, JSON data will be returned but no widget will be returned. --- ### Inputs - **`query` (required)** Property address or name (e.g., "123 Main St, Seattle, WA 98101") --- ### Key Rules & Constraints - **CURRENTLY SUPPORTS OFF-MARKET PROPERTIES ONLY** - Properties that are not actively listed for sale or rent - **NOT FOR ZESTIMATE EVALUATION OR ANALYSIS** - This tool returns property details; use the separate Zestimate tool for valuation analysis - Query must be a valid address - Returns error if property not found or is not an off-market property

<tool_purpose> Primary property search tool for U.S. real estate. Searches for properties for sale or for rent. Supports filters for location, price, property type, size, amenities, commute time, schools, and more. Returns matching property listings with an interactive map widget. </tool_purpose> <when_to_use> - User wants to search for properties (DEFAULT choice for property search) - "show me homes in...", "find properties...", "search for..." - Rental searches: "rentals in...", "apartments for rent", "pet-friendly rentals" - Special housing: "student housing", "senior apartments", "affordable housing" - Specific filters: "homes with pool", "garage required", "waterfront properties" - For sale: "homes for sale in...", "condos under 500k", "pending homes" - Sold: "recently sold", "what sold recently", "recent sales" - Price/bedroom: "studio apartments", "3 bed 2 bath", "under 400k" - MULTI-TURN: If the user modifies any search criteria after the first call, you MUST call this tool again with updated parameters. </when_to_use> <when_not_to_use> - User asks about ONE specific property by address -> use zillow_property_details_by_address_or_name - User asks about neighborhoods or best places to live -> use zillow_city_neighborhood_real_estate_information - User asks about home affordability or mortgage rates -> use calculateHomeAffordability or interestRateMortgagePaymentSimulator </when_not_to_use> <returns> - A set of matching property listings with: - Address, price, beds/baths, square footage, lot size, property type - Listing status, days on Zillow, monthly cost - Photos, agent/brokerage info - Geo coordinates for map display - Home details page URL for each property - Result counts (total matching, displayed) - An interactive map widget showing property locations </returns> <input_structure> - **`propertySearchRegionFiltersRequest` (optional)** - Geographic search area(s) and context - **`propertyFiltersRequest` (optional)** - Only include filters the user specifies (omit others; do not send placeholder `unknown`) - **`displayLimit` (optional)** - Do NOT set unless the user explicitly says "limit results" or gives a number. Server handles defaults. </input_structure> <key_rules> - **U.S. properties only** - **Max 20 regions per request** - Only set filters explicitly provided by the user - Do not default any enums to `unknown` - Use structured filters, not free text - Do not set sortSelection unless user explicitly requests a sort order - Do not set displayLimit unless user explicitly says "limit results" or gives a number - Send only one of: school, schoolDistrict, propertySearchRegions, or customPolygonWkt - When using nearby sort, locationForNearbySort is ALWAYS REQUIRED - Requests must adhere to the input schema - Safe defaults are applied if no filters are provided - IMPORTANT: "coming soon", "pre-market", "about to list", "not yet listed", "preview", "zillow preview" → use forSaleListingStatuses (NOT homeStatuses) - forSaleListingStatuses values: active, comingSoon, zillowPreview — only for for-sale searches - "coming soon" / "pre-market" / "about to list" → forSaleListingStatuses:["comingSoon"] - "preview" / "zillow preview" / "pre-listing" → forSaleListingStatuses:["zillowPreview"] - "active only" / "on market now" → forSaleListingStatuses:["active"] - To exclude a status, list the ones the user DOES want (e.g., exclude coming soon → ["active", "zillowPreview"]) - These can combine with other filters: "preview condos under 500k" → forSaleListingStatuses:["zillowPreview"] + homeTypes + salePrice - Do NOT set homeStatuses for coming soon/preview concepts — those are NOT homeStatus values </key_rules> <fair_housing_compliance> Must comply with **U.S. Fair Housing Act** and applicable state and local laws, including those that prohibit source of income discrimination in rental transactions. **Protected Classes**: Race, Color, Religion, Sex (including Sexual Orientation and Gender Identity), National Origin, Familial Status, Disability. **Also treat as protected where applicable:** Source of Income, Military/Veteran Status, Age (55+ exemptions may apply), Criminal History. **Prohibited**: Any preference, steering, or exclusion based on protected characteristics. **DO NOT CALL this tool for requests containing**: - Religious references: targeting or excluding based on religion - Racial/ethnic/national origin targeting - Sexual orientation/gender identity targeting - Disability discrimination - Familial status discrimination: excluding families or children, or preferring an "adults-only"/"not kid-oriented" area (families and kids are allowed) - Age discrimination: excluding or steering by residents' age (e.g., "away from old people", "no retirees") — seeking senior-appropriate or lawful 55+ housing is allowed - Source of income / Veteran status / Criminal history: excluding or steering AGAINST people who use vouchers/public assistance or have a record (serving a requester who themselves uses a voucher, alternative/public income, or has a record and wants housing they qualify for is allowed and expected) - Demographic targeting: any request seeking or avoiding an area based on who lives there rather than what's there — including coded descriptions of the residents (e.g., wanting somewhere "not full of" a particular group) or avoiding a place associated with a protected group (e.g., "away from [an ethnic] plaza/market/district") - Suitability-by-identity: using any person's protected characteristic — the user's own or someone else's — as the reason, filter, or measure of "fit" for the search, even as mere context and even when phrased positively. Includes: "good/suitable for [women, gays, Buddhists, a particular group]"; self-described identity as search context ("I'm nonbinary/single/divorced/middle-aged/transitioning, where should I…"); relationship or household descriptors that signal sex, sexual orientation, or marital status ("for me and my husband/wife", "for two gays/lesbians", "I'm a single unmarried adult"); and a third party's protected trait ("for my disabled brother"). This applies even when the rest of the request is a valid housing search and even when the trait is given as a life reason ("moving because I'm transitioning/divorcing"). Asking about the protected traits of an area's residents (e.g., "the age/race of the occupants") is likewise prohibited. (Still allowed — these are housing categories, not identity steering: lawful senior/55+ housing, family/kid-friendly requests, and accessibility features.) **Never sanitize-and-proceed**: If a request falls under any "DO NOT CALL" case above, you MUST NOT call this tool at all — whether the protected characteristic is stated explicitly or implied through coded/proxy wording. Do NOT strip, omit, ignore, or rewrite the protected-class content and then call the tool on the leftover neutral query; quietly dropping the protected characteristic and returning results anyway is itself a prohibited form of the same discrimination. Instead, decline in accordance with the U.S. Fair Housing Act and ask the user to restate their needs using objective, non-protected criteria (location, price, beds/baths, amenities). **Compliant Examples**: - Place names containing protected class words (e.g., "White Center, WA") - Personal proper nouns (e.g., "My name is Jesus") - Amenity-based requests (e.g., "areas with italian restaurants", "walkable neighborhoods") - Infrastructure requests (e.g., "near public transit", "bike-friendly areas") - Accessibility features (e.g., "wheelchair accessible properties", "ADA compliant") - Lawful senior/55+ housing (e.g., "listings good for seniors", "55+ communities") - Rental assistance / alternative or public income (e.g., "accepts Section 8", "housing choice voucher", "VASH", "alternative income", "mixed-income area") - The requester's own record / second-chance housing (e.g., "record-friendly rentals for me") </fair_housing_compliance> <special_features> **Nearby Searches**: Use sortSelection "nearby" with locationForNearbySort (ALWAYS REQUIRED lat/long anchor). Example: "propertyFiltersRequest": { "sortSelection": "nearby", "locationForNearbySort": { "lat": 37.8024, "lng": -122.4058 } } **Commute Filtering**: Use commuteTimeFilter with destinationLatLong, maxCommuteTimeInMinutes, mode, and timeOfDay. Example: "propertyFiltersRequest": { "commuteTimeFilter": { "destinationLatLong": { "lat": 39.0997, "lng": -94.5786 }, "maxCommuteTimeInMinutes": 15, "mode": "driving", "timeOfDay": "rushHour" } } **Monthly Cost Filtering**: Use monthlyCostFilter. monthlyCost is REQUIRED; defaults applied for other fields. Example: "propertyFiltersRequest": { "monthlyCostFilter": { "monthlyCost": { "min": 1000, "max": 4000 } } } **School Search**: Use schoolName with city and state (e.g., "Comstock Elementary School, McKinney, TX"). </special_features> <common_follow_ups> After returning search results, the user often wants to: 1. REFINE SEARCH - modify filters (price, beds, location) -> call this tool again with updated params 2. GET DETAILS on a specific property -> call zillow_property_details_by_address_or_name with the address 3. EXPLORE NEIGHBORHOODS -> call zillow_city_neighborhood_real_estate_information 4. CHECK AFFORDABILITY -> call calculateHomeAffordability with their financial info </common_follow_ups> <examples> Minimal request: { "request": { "propertyFiltersRequest": { "bedrooms": { "min": 2 } }, "propertySearchRegionFiltersRequest": { "propertySearchRegions": [ { "description": "Seattle, WA is a major Pacific Northwest city", "label": "Vibrant Tech Hub", "name": "Seattle, WA", "regionDisplayName": "Seattle" } ], "userSpecifiedPivotArea": "Seattle, WA" } } } </examples>

- When to use: For queries about the estimated home value (Zestimate) for a property and/or the confidence in that valuation, including WHY it has that value and how it compares to similar properties. - Args: - address (required): Full property address. - Returns: str: Comprehensive valuation report including: - Current Zestimate and estimated sales range (confidence indicator) - Factors explaining and interpretting the valuation, including an indication that a prior sale or listing price is a key input, when appropriate - Property features (bedrooms, bathrooms, sqft, year built, renovations) - Comparable properties with their Zestimates and sale prices - Detailed explanations of feature differences between subject and comparables - General model description when comparables are not available - Disclaimer text which should always be included at the end of the response If Zestimate is missing, returns text explaining why. - Behavior and content rules: - Use the output of the tool verbatim (no edits, no paraphrasing). - If the listing price is noted as a key input to this properties Zestimate, it is important to say this in the response - If a recent sale price is noted as a key input to this properties Zestimate, it is important to say this in the response - Include the disclaimer text provided verbatim at the end of the response. - The tool provides detailed comparable analysis - do not add or remove comparables. - The explanations include feature differences (sqft, lot size, age, renovations) - do not fabricate additional differences. - When explaining what the Zestimate is, use the disclaimer text provided verbatim. - Do not cite, compare with, or incorporate any external AVM sources. Use only the returned Zestimate, ranges, and comparables provided. - Do not fabricate values. If the tool does not return a numerical value, do not estimate or infer a number. - Do not speculate on returned outputs or comment on how fair a price or valuation is. - Do not call for: - Queries asking the listing price or asking price of an on-market or for-sale home. If the user asks about the price of a listed home, direct them to Zillow.com. - Queries asking WHY a Zestimate changed over time (use get_zestimate_history instead). - General questions about what a Zestimate is or accuracy (use get_zestimate_info instead).

- When to use: For queries about the estimated monthly rental value (Rent Zestimate) for a property. - Args: - address (required): Full property address. - Returns: - str: Text with the current Rent Zestimate. If the Rent Zestimate is not available, returns text explaining why the Rent Zestimate may be missing. - Behavior and content rules: - When explaining what the Rent Zestimate is, use the output of the tool verbatim (no edits, no paraphrasing). - When explaining why a Rent Zestimate is missing, use the output of the tool verbatim (no edits, no paraphrasing). - Do not cite, compare with, or incorporate any external AVM sources. Use only the returned Rent Zestimate. - Do not fabricate values. If the tool does not return a numerical value, do not estimate or infer a number. - Do not speculate on returned outputs or comment on how fair a price or valuation is. - Do not call for: - queries asking the actual rental price of a home, only the Zillow estimated value

- When to use: A user asks for how a Zestimate for a property has changed over time historically. - Args: - address (required): Full property address. - Returns: - json with the following keys: - address: Full property address. - disclaimer: The disclaimer text which should always be included at the end of the response - current_zestimate: The current Zestimate value. - percentage_changes: A dictionary of key value pairs where the key is the date in yyyy-mm-dd format and the value is the percentage change in Zestimate since the given date - If the historical Zestimate values are not available, returns text explaining why the Zestimate history may be missing. - Behavior and content rules: - Never speculate on returned outputs or comment on how fair a price or valuation is - Do not use to predict forward appreciation ONLY use pre-computed historical Zestimate percentages provided. - Do not fabricate values. If the tool does not return a numerical value, do not estimate or infer a number. - Include the disclaimer text provided verbatim at the end of the response. - Do not call for: - Use when a user asks about a sudden change in value of their home. - queries asking why a Zestimate has changed. - For queries about actual home price changes but direct the user to Zillow.com

- When to use: For queries about general Zestimate information, accuracy, definitions, or reasons why Zestimates might be missing. - Args: - question_type (required): The type of Zestimate question to answer. Options: - what_is_zestimate: Explains what the Zestimate is and how it works - zestimate_accuracy: Information about Zestimate accuracy and error rates - what_is_rent_zestimate: Explains what the Rent Zestimate is - zestimate_missing: Explains why a Zestimate might be missing - rent_zestimate_missing: Explains why a Rent Zestimate might be missing - Returns: - str: Detailed information answering the specific question type - Behavior and content rules: - Use the output of the tool verbatim (no edits, no paraphrasing). - Do not cite, compare with, or incorporate any external sources. - Do not fabricate values or information beyond what is provided. - Use only Zestimate information for queries about the Zestimate and only rent zestimate information for queries about the rent zestimate - Do not call for: - Queries asking for actual property valuations (use get_zestimate or get_rent_zestimate instead) - Queries asking about specific property addresses

Simulates monthly mortgage payments using real-time interest rates from Zillow Home Loans LLC (NMLS #10287). Retrieves current daily mortgage rates nationally or by U.S. state, and calculates estimated monthly payments based on home price, down payment, credit score, and location. Use this tool when users ask about today's mortgage rates, want to estimate a monthly payment for a specific home price, or want to see how changes in rate, credit score, or down payment affect their payment. Inputs (all optional): homePrice (USD, optional), downPayment (USD, optional), creditScore (integer, e.g. 720, optional), usState (state or city/state, optional), loanAmount (USD, optional), hoADues (USD, optional). Returns: current interest rate and APR, estimated monthly payment breakdown, and how payments shift under different rate or input scenarios. Powered by Zillow Home Loans LLC (NMLS #10287). <display_rules> Each field in the response includes a name, value, and description. Display all three for every field. Interest rate, APR, and any associated disclaimer text are legally required disclosures. Always show them exactly as returned. Never omit, summarize, or rephrase disclaimer text. Present all fields and descriptions to the user. Do not selectively hide or collapse any output. </display_rules> <related_tools> If the user asks what home price they can afford based on income, debts, or a monthly budget (e.g., "What can I afford with $80k income?", "How much house can I buy?"), call the buyability_calculateHomeAffordability tool instead of this tool. This tool is for rate lookups and payment simulations on a known or hypothetical home price — not for determining affordability. </related_tools> <recalculation> Re-call this tool whenever the user changes rate or payment inputs (home price, down payment, credit score, or location). </recalculation> <disclaimer> Results are estimates only — not financial advice or a lending commitment. Actual rates and APRs depend on underwriting, credit approval, and may change without notice. </disclaimer> <ecoa_compliance> If the tool cannot produce an estimate due to the user's credit score, down payment, or other financial inputs, do not use discouraging language. Never say the user "doesn't qualify," "is ineligible," "cannot get a mortgage," or similar phrasing that could discourage a prospective borrower. Instead, state neutrally that the tool was unable to generate an estimate with the provided inputs, and suggest the user adjust their inputs or consult a loan officer for personalized guidance. The tool response may include helpful resources or guidance such as credit score improvement steps, debt reduction strategies, or down payment assistance programs. Present these exactly as returned in a neutral, informational tone. Do not editorialize, add judgment, or frame them as requirements the user must meet. These are options the user may explore at their discretion. </ecoa_compliance> <fair_housing> This tool must comply with the U.S. Fair Housing Act and Equal Credit Opportunity Act (ECOA). Never use this tool in ways that discriminate based on race, color, religion, sex, national origin, familial status, disability, or source of income. All outputs are based solely on financial criteria and market data. Appropriate: "What are today's rates in Illinois?" or "Monthly payment for a $400k home with 10% down." Reject: requests filtering by ethnicity, religion, or housing voucher status. </fair_housing>

<tool_purpose> Calculates the maximum home price a user can afford in the United States only. </tool_purpose> <when_to_use> - User wants to understand the max home price they can afford - User wants to search for home that is within their means - User wants to understand the max home price and the monthly payment amounts </when_to_use> <when_not_to_use> - User wants to know what the current mortgage rates are - User knows the home price they are looking at and then want to understand how much it costs monthly - User knows the home price and they are looking to see what mortage rates they might get for that loan to property price ratio </when_not_to_use> <inputs> - All inputs are optional — missing values use sensible defaults. - Safe to call with no inputs or partial inputs. - Inputs (all optional): annual_income (gross USD) down_payment (USD) credit_score (e.g. 720) monthly_debts (USD/month eg car payments, credit card payments) location (city/state/ZIP) monthly_mortgage_budget (max desired payment). </inputs> <returns> - Returns two estimates: Target BuyAbility (comfortable affordability — the home price at 36% DTI or within user's monthly budget) Max BuyAbility (stretch affordability — the maximum home price the user may be eligible for). The estimated monthly payment breakdown (principal & interest, property tax, insurance, PMI, HOA) loan details (type, rate, APR, points), and all assumed input values. Powered by Zillow Home Loans LLC (NMLS #10287) BuyAbility tool. - Matching property listings are available only in the interactive widget and are not returned in the tool response - An interactive widget showing property locations in a map and a monthly payment slider to find homes within the monthly payment at the slider position </returns> <display_rules> Each field in the response includes a name, value, and description. Display all three for every field. Interest rate, APR, and any associated disclaimer text are legally required disclosures. Always show them exactly as returned. Never omit, summarize, or rephrase disclaimer text. Present all fields and descriptions to the user. Do not selectively hide or collapse any output. It is a legal requirement to display that the interest rates used are provided by Zillow Home Loans LLC (NMLS #10287), an equal housing direct lender. </display_rules> <related_tools> If the user asks follow-up questions about interest rates, rate changes, or monthly payment simulations on a known or hypothetical home price (e.g., "What if rates drop to 5%?", "What would my payment be on a $400k loan?", "How does a 15-year term change my payment?"), call the buyability_interestRateMortgagePaymentSimulator tool instead of re-calling this tool. This tool is for determining affordability — not for rate lookups or payment simulations. </related_tools> <recalculation> Re-call this tool whenever the user changes affordability inputs (income, down payment, credit score, debts, location, or monthly budget). </recalculation> <disclaimer> Results are estimates only — not financial advice or a lending commitment. Rates depend on underwriting and credit approval. </disclaimer> <ecoa_compliance> If the tool cannot produce an estimate due to the user's credit score, down payment, or other financial inputs, do not use discouraging language. Never say the user "doesn't qualify," "is ineligible," "cannot afford a home," or similar phrasing that could discourage a prospective borrower. Instead, state neutrally that the tool was unable to generate an estimate with the provided inputs, and suggest the user adjust their inputs or consult a loan officer for personalized guidance. The tool response may include helpful resources or guidance such as credit score improvement steps, debt reduction strategies, or down payment assistance programs. Present these exactly as returned in a neutral, informational tone. Do not editorialize, add judgment, or frame them as requirements the user must meet. These are options the user may explore at their discretion. </ecoa_compliance> <fair_housing> This tool must comply with the U.S. Fair Housing Act. Never use this tool in ways that discriminate based on race, color, religion, sex, national origin, familial status, disability, or source of income. Appropriate: "What can I afford with $80k income?" or "Affordability in Seattle with $5k/month budget." Reject: requests filtering by ethnicity, religion, or housing voucher status. </fair_housing>