real-estate-mcp-server
Server Details
Redfin listings, sale-comps, and neighborhood market data via natural-language queries.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.4/5 across 2 of 2 tools scored.
The two tools have clearly distinct purposes: one searches for properties based on criteria, the other retrieves detailed information for a specific property using a URL. There is no overlap in functionality.
Both tool names follow the verb_noun pattern consistently (search_redfin_properties, get_property_details), making the set predictable and easy to understand.
With only two tools, the server covers basic property research but feels limited for a comprehensive real estate MCP server. More tools (e.g., for comparing properties, market trends) could be expected.
The server covers the core read-only workflow of searching for properties and retrieving details. Minor gaps exist, such as the absence of tools for price history or neighborhood data, but these are not critical for the stated purpose.
Available Tools
2 toolsget_property_detailsARead-onlyInspect
Retrieve comprehensive details for a specific property from Redfin URL. Returns full description, tax history, HOA fees, walk scores, nearby schools, crime statistics, and property photos/virtual tour link. Use for due diligence, investment research, or detailed listing analysis.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Direct Redfin listing URL or property page link (e.g. 'https://www.redfin.com/CA/San-Francisco/123-Main-St') |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations (readOnlyHint, openWorldHint), description details return items: full description, tax history, HOA fees, walk scores, schools, crime, photos, virtual tour. No contradictions, and it adds significant behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences: action and source, return contents, use cases. No redundant information, each sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With only one parameter, no output schema, and clear annotations, the description sufficiently covers purpose, return data, and use cases. No gaps for this simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single parameter 'url'. The description does not add extra parameter details beyond what is in the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Retrieve comprehensive details for a specific property from Redfin URL', using a specific verb and resource. It distinguishes from sibling 'search_redfin_properties' by focusing on a single property via URL.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description provides explicit use cases ('due diligence, investment research, detailed listing analysis') but lacks explicit when-not-to-use guidance. The context signals and sibling tool name imply that searching multiple properties would use the sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_redfin_propertiesARead-onlyInspect
Search Redfin's real estate database for property listings by location and criteria. Returns price, street address, number of bedrooms, bathrooms, square footage, lot size, property type, and listing status. Use for residential property research, investment analysis, or market comparison.
| Name | Required | Description | Default |
|---|---|---|---|
| location | Yes | Property location by address, city, or zip code (e.g. 'San Francisco, CA', '94105', '123 Main St') | |
| max_price | No | Maximum asking price in USD (e.g. 750000 for $750k ceiling) | |
| min_price | No | Minimum asking price in USD (e.g. 250000 for $250k floor) | |
| property_type | No | Type of property to filter (e.g. 'house', 'condo', 'townhouse', 'multi-family') |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds value by specifying the data returned (price, address, bedrooms, etc.), enhancing behavioral understanding beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no wasted words. Front-loaded with core action and resource. Efficient and clear.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given tool simplicity and no output schema, description lists key return fields. Covers location, price, property type filters. Lacks mention of pagination or result limits, but acceptable for a search tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with detailed descriptions (e.g., location examples, price ranges). The description adds no parameter-specific detail beyond summarizing return fields, so it does not significantly augment the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Search') and resource ('Redfin's real estate database'), and distinguishes from sibling 'get_property_details' by focusing on search listings vs. details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear use cases: 'residential property research, investment analysis, or market comparison'. Does not explicitly state when not to use or contrast with sibling, but context is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!