Real Estate Analyzer

Rank the best use of a property

best_use

Read-onlyIdempotent

Screen ONE property across every strategy the provided inputs qualify for and rank them by deal score — answers "what is the best use of this property?". Provide a superset of inputs (price, marketRent, adr, occupancy, rehabBudget, arv, units, …); strategies missing inputs are skipped with reasons. All rates/percents are FRACTIONS (0.0675 = 6.75%). Omitted operating inputs are filled with documented defaults and listed in assumptions.estimated_fields. Free, no key.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`inputs`	Yes	Deal inputs in camelCase engine keys. Anything omitted gets a documented default, listed back under assumptions.estimated_fields. Send a SUPERSET across strategies — whatever you know. Strategies missing their required fields are skipped with a reason rather than failing the call.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`ranked`	Yes
`skipped`	No
`best_use`	Yes	Highest-scoring strategy id.
`data_note`	No	REIzer data tools that can refine this analysis (needs an API key).
`disclaimer`	No	Not financial advice — software estimate only.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 7, 2026

addedOutput schema / properties / data_note

Added value: +{
+  "description": "REIzer data tools that can refine this analysis (needs an API key).",
+  "type": "string"
+}

Changed1 schema field changedAug 6, 2026

addedOutput schema / properties / disclaimer

Added value: +{
+  "description": "Not financial advice — software estimate only.",
+  "type": "string"
+}

Changed4 schema fields changedAug 6, 2026

addedInput schema / properties / inputs / additionalProperties
```
Added value: +true
```

changedInput schema / properties / inputs / description

Previous value: -"One property's inputs — a superset across strategies."New value: +"Deal inputs in camelCase engine keys. Anything omitted gets a documented default, listed back under assumptions.estimated_fields. Send a SUPERSET across strategies — whatever you know. Strategies missing their required fields are skipped with a reason rather than failing the call."

addedInput schema / properties / inputs / properties

Added value: +{
+  "adr": {
+    "description": "Average nightly rate in dollars. Required for str.",
+    "type": "number"
+  },
+  "arv": {
+    "description": "After-repair value in dollars. Required for brrr and flip.",
+    "type": "number"
+  },
+  "btsArv": {
+    "description": "Finished build-to-sell value in dollars. Required for newc.",
+    "type": "number"
+  },
+  "buildPsf": {
+    "description": "Build cost per square foot in dollars. Required for newc.",
+    "type": "number"
+  },
+  "downPct": {
+    "description": "Down payment. Expressed as a FRACTION (0.0675 = 6.75%), never a percent. Optional — a documented default applies.",
+    "type": "number"
+  },
+  "insurance": {
+    "description": "Annual insurance in dollars. Optional.",
+    "type": "number"
+  },
+  "landPrice": {
+    "description": "Land acquisition cost in dollars. Required for newc.",
+    "type": "number"
+  },
+  "livingSqft": {
+    "description": "Heated living area in square feet. Required for newc.",
+    "type": "number"
+  },
+  "marketRent": {
+    "description": "Expected monthly rent in dollars. Required for ltr and brrr.",
+    "type": "number"
+  },
+  "occupancy": {
+    "description": "Expected occupancy. Expressed as a FRACTION (0.0675 = 6.75%), never a percent. Required for str.",
+    "type": "number"
+  },
+  "price": {
+    "description": "Purchase price in dollars. Required for every strategy except newc.",
+    "type": "number"
+  },
+  "rate": {
+    "description": "Annual interest rate. Expressed as a FRACTION (0.0675 = 6.75%), never a percent. Optional.",
+    "type": "number"
+  },
+  "rehabBudget": {
+    "description": "Renovation budget in dollars. Required for brrr and flip.",
+    "type": "number"
+  },
+  "taxes": {
+    "description": "Annual property taxes in dollars. Optional.",
+    "type": "number"
+  },
+  "term": {
+    "description": "Loan term in years. Optional.",
+    "type": "number"
+  },
+  "units": {
+    "description": "Multifamily rent roll — {unitCount, avgRent, marketRent?} or an array of unit objects. Required for multifamily.",
+    "type": "object"
+  },
+  "vacancyPct": {
+    "description": "Vacancy allowance. Expressed as a FRACTION (0.0675 = 6.75%), never a percent. Optional.",
+    "type": "number"
+  }
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "best_use": {
+      "description": "Highest-scoring strategy id.",
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "ranked": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "skipped": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "best_use",
+    "ranked"
+  ],
+  "type": "object"
+}

First observedAug 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, idempotentHint, and destructiveHint, but the description goes further: it warns that all rates/percents are fractions, states that omitted inputs are filled with documented defaults and listed in assumptions.estimated_fields, and notes it is free with no key. These are valuable behavioral details beyond what annotations provide.

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 compact and front-loaded with the core purpose, followed by essential operational guidance (superset input, fractions, defaults, no key). Every sentence contributes meaningful information; there is no fluff or repetition of schema details.

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?

Given the complex nested schema and multiple strategies, the description covers key behavior: skipping missing strategies, default handling, fraction convention, and where defaults are reported. An output schema exists, so return structure doesn't need explanation, and the description is complete enough for an agent to select and invoke the tool 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?

The input schema has 100% description coverage, so the baseline is 3. The description adds critical global semantics not uniformly present in the schema: sending a superset, all rates being fractions, and omitted fields getting defaults. This elevates the value beyond the structured 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 states a specific verb and resource: 'Screen ONE property across every strategy...' and 'rank them by deal score', directly answering 'what is the best use of this property?'. It distinguishes itself from siblings like analyze_deal (single-deal analysis) and list_strategies (strategy listing).

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?

It clearly instructs to 'Provide a superset of inputs' and explains that strategies missing inputs are skipped with reasons, which is key usage guidance. It doesn't explicitly mention when not to use it or alternative tools, but the 'best use' framing and sibling context make the intended use clear.

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

All Real Estate Analyzer 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?