Neighborhood-baseline property value estimate. Returns the Census ACS median home value for the zip plus a wide confidence interval. NOT an individual-property AVM — does not adjust for sqft, beds, lot, condition, or recent comps. Use this to ground-truth a buyer's expectation; pair with scout.search_listings for actual sold/active comps. Free, all 50 states.
| Name | Required | Description | Default |
|---|---|---|---|
| zip | Yes | 5-digit ZIP code. Required. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It transparently states that the result is a wide confidence interval, not a precise value, and does not adjust for property-specific features. It also specifies the data source (Census ACS).
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 three sentences, each serving a purpose: defining the tool, clarifying its limitations, and providing usage guidance. No unnecessary words.
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?
The description adequately explains the tool's behavior and limitations given its simplicity. However, without an output schema, it does not detail the exact return fields (e.g., median value, confidence interval range), leaving minor ambiguity. Still, it is mostly complete.
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 covers the single parameter (zip) with a clear description. The tool description does not add additional semantics beyond stating that zip is required, but since schema coverage is 100%, a baseline score of 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?
The description clearly states the tool returns a neighborhood-baseline property value estimate using Census ACS median home value, and explicitly distinguishes it from an individual-property AVM. It also contrasts with scout.search_listings, making its purpose unambiguous relative to siblings.
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 provides explicit guidance on when to use the tool ('ground-truth a buyer's expectations') and recommends pairing it with scout.search_listings for actual comps. It also notes it is free and available in all 50 states, aiding decision-making.
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.
Each tool has a clearly distinct purpose, from agent profiles and comparisons to market data and lead management. Overlaps like find_agent vs find_public_agent are explicitly differentiated by live vs directory status.
All tools use snake_case and the 'scout.' prefix, but they mix verb_noun (e.g., compare_agents, search_listings) and noun_noun (e.g., agent_profile, coverage) patterns. However, the naming remains predictable and readable overall.
With 18 tools, the server covers agent discovery, brokerage info, market data, listings, lead management, referrals, and licensing—well-scoped for a real estate assistant without redundancy.
The tool set covers all key workflows: agent and brokerage search, market insights, school data, listing search, lead generation and purchase, referral management, and license verification, with no obvious gaps for its domain.
