Homesage.ai MCP

Get Property Info

get_property_info

Read-only

What it returns

Full property record for a single US residential property — address, coordinates, listing status and price, AVM-estimated value, size, days on market, building/lot/parking/interior breakdown, listing-office details, recent property history, and nearby school ratings. Sourced from a national listing graph + Homesage.ai's AVM, hydrated on the first call per property and cached.

When to use it

Render a property-detail page in your UI.
Enrich a CRM lead record with the latest listing status and AVM.
Cross-check a third-party AVM against Homesage.ai's.
Look up listing-office contact info from a property address.

Pricing

2 credits per successful call. null returns from missing source data still cost 2 credits because the upstream call still ran. 404/401/402 cost 0 credits.

Errors

Status	Meaning
400	Neither `property_address` nor `property_id` provided, or `property_id` is not valid base64.
401	Authentication failed.
402	No subscription, or out of credits.
404	The autocomplete suggestion didn't match a real listing. Response includes `did_you_mean` suggestions.

FAQ

What's the difference between `info` and `updated-info`?

info is the fast lookup and may serve recently stored data. updated-info always returns the freshest available record (slower). Use updated-info when stale data matters — pricing decisions, just-listed alerts, post-sale follow-ups.

Why is `listing_price` `null`?

The property is not currently listed for sale. estimated_value (AVM) is still populated when available.

Can I look up by `property_id` instead of address?

Yes — pass property_id as a base64-encoded string. Use the id field returned by auto-complete.

How fresh are school ratings?

Refreshed annually from national school-ratings data.

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": {
      "property_address": "<property_address>"
    },
    "name": "get_property_info"
  }
}

Input Schema

Name	Required	Description	Default
`property_address`	Yes	Full US property address to look up.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds substantial context beyond readOnlyHint/openWorldHint/destructiveHint: 2-credit cost per call, that null results still bill, that 404/401/402 are free, that the record is hydrated on first call and cached, and that 404 returns did_you_mean. The one gap is that 'cached/fast lookup' never quantifies how stale 'recently stored data' is, which is precisely what the info-vs-updated-info decision hinges on.

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

Conciseness4/5

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

Front-loaded and well sectioned into returns / when-to-use / pricing / errors / FAQ, which scans quickly. It runs long and drifts into tangents (annual school-ratings refresh cadence, the listing_price-null explanation) that are closer to documentation prose than selection help.

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 paid, open-world lookup with an output schema, the description covers return contents, cost model, failure modes per status code, and freshness tradeoffs against its sibling. An agent has everything needed to decide whether to call it and what a null or 404 means.

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 coverage is 100% and the single parameter is documented, so baseline is 3. The description does add lookup-by-property_id detail (base64, sourced from auto-complete's id field), but property_id does not appear in the input schema at all while the 400 error text says 'Neither property_address nor property_id provided' — this inconsistency undercuts rather than clarifies parameter usage.

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?

Opens with a concrete verb+resource and enumerates exactly what a single-property record contains (address, coordinates, listing status/price, AVM value, DOM, building/lot/interior, office details, history, school ratings). The FAQ explicitly distinguishes it from the close sibling get_updated_property_info, so an agent can separate the two without reading either schema.

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?

Gives four concrete when-to-use scenarios (detail page, CRM enrichment, AVM cross-check, office lookup) and names the alternative tool with the condition that selects it — 'use updated-info when stale data matters — pricing decisions, just-listed alerts, post-sale follow-ups.'

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