[Redfin Real Estate] Get detailed information for a specific Redfin property listing including price history, description, photos, and nearby data.
Args: url: Full Redfin property URL (e.g. 'https://www.redfin.com/WA/Seattle/...')
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true (safe read) and openWorldHint=true. The description adds concrete details about what is returned (price history, description, photos, nearby data), giving useful behavioral context 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?
The description is concise: a brief intro outlining what the tool provides and a single parameter description. No wasted sentences, front-loaded with key information.
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?
For a simple tool with one parameter and no output schema, the description covers the input requirement and a summary of output content. It could mention output format or possible errors, but is largely complete given the tool's simplicity.
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?
The schema only says 'url' is a string with no description. The description provides a clear explanation: 'Full Redfin property URL' with an example. This adds significant meaning beyond the schema, compensating for 0% schema description coverage.
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 clearly states the verb 'Get' and the resource 'detailed information for a specific Redfin property listing', listing included data (price history, description, photos, nearby data). It distinguishes from sibling tools like redfin__search_properties which is for searching, not getting 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?
The description implies that you need a full Redfin URL to use this tool, but does not explicitly state when to use this vs searching for properties or other siblings. No guidance on prerequisites or alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools have overlapping functionality across categories (e.g., multiple search_arxiv, search_google_scholar, real estate tools, DNS/WHOIS checks). An agent would struggle to differentiate between similar tools from different categories, leading to ambiguity.
Tools follow a 'category__verb_noun' pattern mostly, but verbs vary (get, search, screen, check, etc.) and some categories use different orders (e.g., 'get_repo_stats' vs 'search_repos'). The consistency is acceptable but not uniform across the entire set.
With 152 tools, the server is excessively large for a single MCP server. While it aims to be an all-in-one gateway, the sheer number overwhelms the agent and likely exceeds practical limits for coherent selection.
The server covers a wide range of domains (finance, real estate, news, developer tools, etc.) but has notable gaps (e.g., social media APIs, CRM tools). Coverage is broad but not exhaustive, and some niche areas (e.g., global stock exchanges) are over-represented.