Homesage.ai MCP

Area Autocomplete

area_autocomplete

Read-only

What it returns

Up to 5 area suggestions (city, county, or ZIP) matching a partial place name — each a structured object you pass straight into the location filter of preview_property_search / run_property_search. This is how you turn "Austin" or "Travis County" into the exact object the search needs.

Distinct from auto_complete_address: that resolves a single street address (for the single-property analysis tools); this resolves a search area (a whole city / county / ZIP) for database search.

When to use it

ALWAYS before a property search, to build the location filter. Don't hand-craft area objects — resolve them here so the city name, state_code, and county name match the database.
Pick the suggestion whose type (city / county / postal_code) matches what the user meant, then JSON-encode it as a one-element array for location — e.g. location=[{the chosen suggestion}].

Pricing

Free — 0 credits.

Errors

Status	Meaning
400	`input` missing.
404	No areas matched the input.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "area_autocomplete"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes	Partial area name to resolve — a city, county, or ZIP (e.g. "Austin", "Travis County", "78704"). Street addresses are not returned (use `auto_complete_address` for those).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, but the description adds substantial context: it returns at most 5 suggestions, they are structured objects ready for the `location` filter, the operation is free, and it documents 400/404 error meanings. That goes well beyond the annotations.

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 front-loaded with return behavior, then usage guidance, then pricing and errors. Headings, examples, and the compact error table make it easy to scan, and every section carries actionable information.

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?

For a one-parameter read-only lookup with an output schema and strong annotations, the description covers the remaining gaps: how to use the returned suggestions, how it differs from address autocomplete, pricing, and error cases. Nothing an agent needs in order to call it correctly appears to be missing.

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

Parameters3/5

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

Schema description coverage is 100% for the single `input` parameter, and the schema already includes examples and the street-address exclusion. The description reinforces that semantics but adds no new parameter syntax or constraints beyond what the schema provides, so this sits at the baseline.

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 states a specific verb and resource: it resolves a partial area name into up to 5 city/county/ZIP suggestions for the property-search location filter. It explicitly distinguishes itself from `auto_complete_address`, so an agent can select the right tool without inspecting schemas.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: always call before a property search to build the `location` filter, do not hand-craft area objects, choose the suggestion whose `type` matches user intent, and JSON-encode it as a one-element array. It also names the alternative address autocomplete tool and explains the different use case.

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

All Homesage.ai MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?