Skip to main content
Glama

Homesage.ai MCP

Get Market Outlook

get_market_outlook
Read-only

What it returns

A composite Market Outlook score (0-100) classifying a ZIP code as a buyer's market (<40), balanced (40-60), or seller's market (>60). Built from a hybrid weighted model — 40% macro market indicators (market-heat index and forecasts), 40% Homesage.ai absorption-rate analytics, and 20% live market signals when available. Includes 1/3/6-month forecasts, days-on-market velocity, active/sold/pending counts, and a per-signal breakdown.

When to use it

  • Render a market-context widget on a property report.

  • Power a 'best markets to buy' / 'best markets to sell' ranking.

  • Inform pricing-strategy recommendations.

Pricing

2 credits.

FAQ

What if live market data is unavailable?

The live-signal weight rebalances to the macro and Homesage.ai components (50% / 50%). The response's weights_used field reflects the actual weights applied.

Why ZIP-level instead of city or county?

ZIP is the smallest unit that all three sources support consistently. For city/county roll-ups, query multiple ZIPs and aggregate.

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": {
      "zip": "<zip>"
    },
    "name": "get_market_outlook"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit US ZIP code.
daysNoLookback window. Default 90 days.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses credit cost (2), the 40/40/20 weighting model, and the rebalancing behavior when live signals are missing including the weights_used field that reports it. That fallback disclosure is exactly the kind of behavior an agent cannot infer from annotations or schema.

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?

Headers make it skimmable and most sentences carry real information, but it leads with 'What it returns' rather than a one-line statement of purpose, and the pricing/FAQ blocks are formatted as documentation prose rather than tightened agent-facing guidance.

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 two-parameter read tool with an output schema and full annotation coverage, this is more than sufficient — scoring model, thresholds, fallback weights, cost, and granularity rationale are all present. An agent can decide and call correctly without further context.

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%, so the baseline is 3; both zip and days are already documented in the schema. The FAQ adds genuine meaning for zip (smallest unit supported consistently by all three sources, aggregate multiple ZIPs for city/county), but days receives no elaboration beyond what the schema says.

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 names a specific artifact (a composite Market Outlook score 0-100 with buyer's/balanced/seller's thresholds) and the exact inputs it fuses. It is immediately distinguishable from siblings like get_sold_count_by_zip or get_comps, which return raw counts or comparable sets rather than a scored classification.

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?

A dedicated 'When to use it' section gives three concrete scenarios (market-context widget, best-markets ranking, pricing strategy). It does not state when NOT to use it or name any sibling as the alternative for adjacent needs, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources