Skip to main content
Glama
chrischall

onehome-mcp

by chrischall

Resolve a OneHome listing by street address

onehome_get_by_address
Read-onlyIdempotent

Resolves a free-text street address to a OneHome listing's portal URL and ID. Returns listing details or indicates no match found.

Instructions

Resolve a free-text street address (with optional city/state/zip) to a OneHome listing's canonical portal URL and id in one call. Walks a 2-rung ladder: (1) ListingSuggestionsSearch against the magic-link saved-search scope; (2) when that misses, search-fallback — page-walks the broader saved-search (or raw listings(groupId)) pool bounded by the same groupId and fuzzy-matches input address tokens. Returns { url, listing_id, address, resolved, matched_via } where matched_via: "suggestions" | "search_fallback" reports which rung produced the hit. When no listing matches, returns { resolved: false, error: "no listing found" } rather than throwing. Read-only; safe to call repeatedly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoZIP code, e.g. "28746"
cityNoe.g. "Lake Lure"
stateNoTwo-letter state abbreviation, e.g. "NC"
addressYesStreet address line, e.g. "126 Sleeping Bear Ln".
group_idNoOptional OneHome group id to scope the suggestion search. Defaults to the magic-link session context when present.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description adds significant behavioral details beyond annotations: the two-rung ladder, return object structure ({ url, listing_id, address, resolved, matched_via }), fallback behavior, and non-throwing error handling. No contradictions with annotations exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized, front-loaded with the main purpose, and every sentence earns its place by explaining either the process, return format, or behavioral guarantees.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description fully documents the return format and error behavior. Given the tool's complexity (5 parameters, 2-stage algorithm), the description provides complete context for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 5 parameters with 100% coverage. Description adds value by explaining the default behavior of group_id (defaults to magic-link session) and clarifying address as 'street address line'. This reduces ambiguity beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (resolve a free-text street address), resource (to a OneHome listing), and scope (in one call). It distinguishes from siblings like onehome_get_property (by ID) and onehome_search_properties (broader search) by specifying the unique resolution process.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the two-rung approach and when the tool is safe to call ('Read-only; safe to call repeatedly'). It does not explicitly mention alternatives for bulk resolution, but provides sufficient context for an agent to decide when to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrischall/onehome-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server