Homesage.ai MCP

Get Investment Potential Score

get_investment_potential

Read-only

What it returns

An Investment Potential score for a US residential property — a single investment_potential value on a 0-100 scale, where higher is better. Designed as a first-pass filter for investor screening. The value is null when a score cannot be computed for that property.

When to use it

Rank a watchlist of properties by overall investment quality.
Power a 'top opportunities in your market' feed.

Pricing

3 credits.

FAQ

Is the score a percentage?

No — it's a 0-100 composite index. Higher = better.

Why is the score `null`?

A score could not be computed for that property. Use current-estimate and comps to assess it directly.

Does it account for my financing assumptions?

No — it's a property-level score, not deal-specific. For deal-level returns, use flip-return or rental-long-term.

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_investment_potential"
  }
}

Input Schema

Name	Required	Description	Default
`property_address`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, and the description adds value beyond that: the score is a composite index rather than a percentage, it can be null when incomputable, and it ignores the caller's financing assumptions. Cost (3 credits) is also disclosed. What is missing is any hint about what drives the score or how fresh it is, which keeps it below a 5.

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 with a 'What it returns' section, followed by usage, pricing and an FAQ, so the most important information comes first. The FAQ repeats points already made (null semantics, alternatives) which is mildly redundant but the formatting makes it skimmable.

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

Completeness4/5

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

An output schema exists, so return-shape exposition beyond the null case is unnecessary, and the description covers cost, null semantics, and sibling routing. The one real hole is the address argument, which goes undocumented in both schema and description.

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

Parameters2/5

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

The single parameter property_address has 0% schema description coverage and the description never mentions it at all — no address format, no US-only constraint restated at the parameter level, no behavior for an ambiguous address. With one undocumented parameter, the description should compensate and does not.

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?

States a specific verb and resource — an Investment Potential score for a US residential property on a 0-100 scale — plus its intended role as a first-pass investor screening filter. It also names the siblings it is not (current-estimate, comps, flip-return, rental-long-term), so an agent can place it among a large sibling set.

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?

Has an explicit 'When to use it' section (rank a watchlist, power a top-opportunities feed) and explicitly routes deal-level analysis to flip-return or rental-long-term, and null-score fallbacks to current-estimate and comps. When-to-use, when-not, and named alternatives are all present.

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