A
licenseA
qualityA
maintenanceMultifamily real estate deal analysis — analyze deals, score properties, calculate max offer prices, and look up market data. Four tools for underwriting 2-200 unit apartment properties.
4
252
3
MIT
Real Estate Analyzer
by io.reizer
Server Details
Free real-estate underwriting, no key or account. 6 strategies, stress tests, max offer.
Ownership verified
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
4 toolsanalyze_dealAnalyze a real-estate dealAInspect
Underwrite a real-estate investment deal and get a 0-100 score, verdict, cash flow, cap rate, DSCR, stress tests, break-even thresholds, and a shareable report link. Strategies: ltr (long-term rental), str (short-term rental), brrr, multifamily, flip (fix-n-flip), newc (new construction). All rates/percents are FRACTIONS (0.0675 = 6.75%). Omitted operating inputs are filled with documented defaults and listed in assumptions.estimated_fields. Output is a software estimate, not financial, investment, tax or legal advice — figures are projections to verify, not recommendations. Free, no key; the response includes a shareable report_url.
ParametersJSON 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. Minimum: price + the strategy's income driver (marketRent / adr+occupancy / units / arv / land+build). Call list_strategies for the full per-strategy schema. | |
| strategy | Yes | Investment strategy to analyze. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| score | Yes | 0-100 deal score. |
| levers | No | Top input changes that would each add ~$1,000/yr cash flow (STR). |
| stress | No | Stress scenarios, each with a verdict. |
| metrics | Yes | Headline metrics for this strategy. |
| summary | Yes | Deterministic one-paragraph summary. |
| upfront | No | Cash-into-the-deal / project-cost stack rows {label, amount, kind}. |
| verdict | Yes | Strong / Solid / Thin / Weak. |
| strategy | Yes | |
| breakdown | No | Ordered cash-flow / profit waterfall rows {label, amount, kind}; outflows are negative. |
| data_note | No | REIzer data tools that can refine this analysis (needs an API key). |
| disclaimer | No | Not financial advice — software estimate only. |
| report_url | No | Shareable public report page (30 days). |
| thresholds | No | |
| assumptions | No | estimated_fields lists every input REIzer defaulted. |
| inputs_used | No | The resolved input set the analysis ran on — caller values plus documented defaults. |
| sensitivity | No | Which input drivers move the result most — {driver, range, low_impact, high_impact, swing}, sorted by swing (STR). |
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description goes beyond the sparse annotations (all false hints) by disclosing that the output is a non-authoritative 'software estimate,' that omitted inputs get documented defaults, that rates must be fractions, and that a shareable report_url is returned. This adds meaningful behavioral context not captured in the structured fields.
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 a single, well-organized paragraph that front-loads the purpose, then covers strategies, the fraction rule, defaults, disclaimer, and free access. Every sentence adds distinct information with no redundancy, making it efficient for an agent to parse quickly.
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 tool's complexity (2 params, one deeply nested inputs object, output schema present), the description covers the main purpose, available strategies, input defaults, output nature, and the report URL. It doesn't need to detail the output schema since that is provided separately, but it gives enough context for correct invocation and expectation-setting.
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?
Schema coverage is 100%, and each parameter already has a description in the schema. The description adds a global rule that all rates/percents are fractions and reinforces the default-filling behavior. While much of this is repeated from the schema, the cross-cutting emphasis on fractions is valuable and may prevent common input errors.
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 opens with a specific verb ('Underwrite') and resource ('real-estate investment deal'), then lists concrete outputs (score, verdict, cash flow, cap rate, DSCR, stress tests, break-even thresholds, report link). It also enumerates the supported strategies, making its scope clear and distinguishing it from siblings like list_strategies and solve_max_offer.
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?
The description clearly implies usage when you have a deal and a strategy in mind, and it names the strategies you can pass. It lacks explicit exclusions or references to alternatives (e.g., 'use best_use to pick a strategy'), but the context is strong enough that an agent would know when to invoke this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
best_useRank the best use of a propertyARead-onlyIdempotentInspect
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.
ParametersJSON 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
ParametersJSON 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. |
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.
list_strategiesList strategies and their inputsARead-onlyIdempotentInspect
List every supported strategy with its required and optional input fields. Call this first when unsure which inputs a strategy needs. Free, no key.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| strategies | Yes |
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description adds value beyond these. It discloses that the tool is 'Free, no key' (no authentication required) and that it lists 'every supported strategy,' indicating a complete enumeration without filtering. This supplements the annotation-provided safety profile.
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 two concise sentences that front-load the main action, immediately state the usage recommendation, and add a practical note about cost/authentication. Every sentence provides distinct value, and there is no verbosity or repetition.
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?
This is a simple, parameterless tool with rich annotations (readOnly, idempotent, non-destructive) and an output schema. The description covers the full scope: what it lists, when to use it, and access requirements. No additional context is needed for an agent to correctly select and invoke this tool.
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 tool has zero parameters, and the schema is empty (100% coverage by default). The per-rubric baseline for 0 parameters is 4. The description does not need to explain parameter semantics, but it does clarify what the output contains (required and optional input fields per strategy), which adds useful context.
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 clearly states the tool's purpose: 'List every supported strategy with its required and optional input fields.' The verb 'list' and resource 'strategies' are specific, and the scope 'every supported strategy' distinguishes it from the sibling analysis/optimization tools. It unambiguously describes a discovery/metadata operation.
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?
The description provides explicit usage guidance: 'Call this first when unsure which inputs a strategy needs.' This establishes a clear use case and priority, though it does not explicitly name alternative tools or exclusion criteria. The guidance is clear and actionable, fitting a score of 4.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
solve_max_offerSolve the maximum offerARead-onlyIdempotentInspect
Reverse-solve the Maximum Allowable Offer: the highest purchase price that still meets every return target (defaults: CoC 8%, DSCR 1.20, cash flow ≥ 0; flip: 10% after-tax margin + 15% annualized ROI). Returns the MAO, the binding constraint, and per-target price ceilings. Strategies: ltr, str, brrr, multifamily, flip. Provide the deal inputs WITHOUT committing to a price (use arv or an asking price as reference). Override targets via the targets object. 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.
ParametersJSON 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. price is optional here — the asking price or ARV anchors the price-derived defaults while the solver searches. | |
| targets | No | Return targets the price must still satisfy. Omit to use each strategy's defaults. | |
| strategy | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| mao | Yes | Maximum allowable offer in dollars. |
| summary | Yes | |
| strategy | No | |
| disclaimer | No | Not financial advice — software estimate only. |
| metrics_at_mao | No | |
| binding_constraint | No | |
| ceilings_per_target | No |
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive. The description adds valuable behavioral context: it fills omitted inputs with the listed defaults, returns the binding constraint, and notes 'Free, no key.' This goes beyond the annotation safety profile.
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?
The description is dense but each sentence adds a distinct piece of information: purpose, output, strategies, input usage, targets, fraction convention, default fill behavior, and cost. It is front-loaded with the primary purpose and avoids filler.
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 complexity of the tool (multiple strategies, nested inputs, targets, defaults), the description covers purpose, usage, parameter conventions, default behavior, and output. The presence of an output schema means return-value details are captured there, so the description is complete for invocation.
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 schema already covers many parameter descriptions, but the description adds cross-cutting semantics: all rates are fractions, inputs without a price anchor use ARV/asking price, and the targets object can override defaults. This helps the agent set the correct parameter values, especially the nested objects.
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 opens with an explicit verb and resource: 'Reverse-solve the Maximum Allowable Offer: the highest purchase price that still meets every return target.' It further specifies the output (MAO, binding constraint, per-target price ceilings) and lists supported strategies, clearly distinguishing it from siblings like analyze_deal.
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?
The description gives clear context for when to use the tool ('Provide the deal inputs WITHOUT committing to a price') and explains how to override targets. It does not explicitly name alternative sibling tools, but the usage context is unambiguous enough for an agent to select it appropriately.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
analyze_deal4 fields changed- added
Output schema / properties / breakdownAdded value: +{ + "description": "Ordered cash-flow / profit waterfall rows {label, amount, kind}; outflows are negative.", + "items": { + "additionalProperties": true, + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / leversAdded value: +{ + "description": "Top input changes that would each add ~$1,000/yr cash flow (STR).", + "items": { + "additionalProperties": true, + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / sensitivityAdded value: +{ + "description": "Which input drivers move the result most — {driver, range, low_impact, high_impact, swing}, sorted by swing (STR).", + "items": { + "additionalProperties": true, + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / upfrontAdded value: +{ + "description": "Cash-into-the-deal / project-cost stack rows {label, amount, kind}.", + "items": { + "additionalProperties": true, + "type": "object" + }, + "type": "array" +}
1 tool update
- Changed
analyze_deal1 field changed- added
Output schema / properties / inputs_usedAdded value: +{ + "additionalProperties": true, + "description": "The resolved input set the analysis ran on — caller values plus documented defaults.", + "type": "object" +}
2 tool updates
- Changed
analyze_deal1 field changed- added
Output schema / properties / data_noteAdded value: +{ + "description": "REIzer data tools that can refine this analysis (needs an API key).", + "type": "string" +}
- Changed
best_use1 field changed- added
Output schema / properties / data_noteAdded value: +{ + "description": "REIzer data tools that can refine this analysis (needs an API key).", + "type": "string" +}
2 tool updates
- Removed
pull_comps - Removed
str_market_data
3 tool updates
- Changed
analyze_deal1 field changed- added
Output schema / properties / disclaimerAdded value: +{ + "description": "Not financial advice — software estimate only.", + "type": "string" +}
- Changed
best_use1 field changed- added
Output schema / properties / disclaimerAdded value: +{ + "description": "Not financial advice — software estimate only.", + "type": "string" +}
- Changed
solve_max_offer1 field changed- added
Output schema / properties / disclaimerAdded value: +{ + "description": "Not financial advice — software estimate only.", + "type": "string" +}
4 tool updates
- Changed
analyze_deal4 fields changed- added
Input schema / properties / inputs / additionalPropertiesAdded value: +true - changed
Input schema / properties / inputs / descriptionPrevious value: -"Deal inputs (camelCase engine keys — call list_strategies for each strategy's schema). Minimum: price + the income driver (marketRent / adr+occupancy / units / arv / land+build)."New value: +"Deal inputs in camelCase engine keys. Anything omitted gets a documented default, listed back under assumptions.estimated_fields. Minimum: price + the strategy's income driver (marketRent / adr+occupancy / units / arv / land+build). Call list_strategies for the full per-strategy schema." - added
Input schema / properties / inputs / propertiesAdded 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" + } +} - changed
Output schema / (root)Previous value: -nullNew value: +{ + "additionalProperties": true, + "properties": { + "assumptions": { + "additionalProperties": true, + "description": "estimated_fields lists every input REIzer defaulted.", + "type": "object" + }, + "metrics": { + "additionalProperties": true, + "description": "Headline metrics for this strategy.", + "type": "object" + }, + "report_url": { + "description": "Shareable public report page (30 days).", + "type": "string" + }, + "score": { + "description": "0-100 deal score.", + "type": "number" + }, + "strategy": { + "type": "string" + }, + "stress": { + "description": "Stress scenarios, each with a verdict.", + "items": { + "additionalProperties": true, + "type": "object" + }, + "type": "array" + }, + "summary": { + "description": "Deterministic one-paragraph summary.", + "type": "string" + }, + "thresholds": { + "additionalProperties": true, + "type": [ + "object", + "null" + ] + }, + "verdict": { + "description": "Strong / Solid / Thin / Weak.", + "type": "string" + } + }, + "required": [ + "strategy", + "score", + "verdict", + "metrics", + "summary" + ], + "type": "object" +}
- Changed
best_use4 fields changed- added
Input schema / properties / inputs / additionalPropertiesAdded value: +true - changed
Input schema / properties / inputs / descriptionPrevious 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." - added
Input schema / properties / inputs / propertiesAdded 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" + } +} - changed
Output 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" +}
- Changed
list_strategies1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "additionalProperties": true, + "properties": { + "strategies": { + "items": { + "additionalProperties": true, + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "strategies" + ], + "type": "object" +}
- Changed
solve_max_offer7 fields changed- added
Input schema / properties / inputs / additionalPropertiesAdded value: +true - changed
Input schema / properties / inputs / descriptionPrevious value: -"Deal inputs (price optional — arv/asking anchors the defaults)."New value: +"Deal inputs in camelCase engine keys. Anything omitted gets a documented default, listed back under assumptions.estimated_fields. price is optional here — the asking price or ARV anchors the price-derived defaults while the solver searches." - added
Input schema / properties / inputs / propertiesAdded 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" + } +} - added
Input schema / properties / targets / additionalPropertiesAdded value: +true - changed
Input schema / properties / targets / descriptionPrevious value: -"Optional target overrides, e.g. {\"cocReturn\": 0.10, \"dscr\": 1.25}."New value: +"Return targets the price must still satisfy. Omit to use each strategy's defaults." - added
Input schema / properties / targets / propertiesAdded value: +{ + "afterTaxAnnualROI": { + "description": "Flip: minimum annualized after-tax ROI. Expressed as a FRACTION (0.0675 = 6.75%), never a percent.", + "type": "number" + }, + "afterTaxMargin": { + "description": "Flip: minimum after-tax profit margin. Expressed as a FRACTION (0.0675 = 6.75%), never a percent.", + "type": "number" + }, + "capitalRecovery": { + "description": "BRRRR: minimum share of invested cash returned at refi. Expressed as a FRACTION (0.0675 = 6.75%), never a percent.", + "type": "number" + }, + "cocReturn": { + "description": "Minimum cash-on-cash return. Expressed as a FRACTION (0.0675 = 6.75%), never a percent.", + "type": "number" + }, + "dscr": { + "description": "Minimum debt-service coverage ratio, e.g. 1.25.", + "type": "number" + }, + "monthlyCF": { + "description": "Minimum monthly cash flow in dollars.", + "type": "number" + } +} - changed
Output schema / (root)Previous value: -nullNew value: +{ + "additionalProperties": true, + "properties": { + "binding_constraint": { + "additionalProperties": true, + "type": "object" + }, + "ceilings_per_target": { + "additionalProperties": true, + "type": "object" + }, + "mao": { + "description": "Maximum allowable offer in dollars.", + "type": "number" + }, + "metrics_at_mao": { + "additionalProperties": true, + "type": "object" + }, + "strategy": { + "type": "string" + }, + "summary": { + "type": "string" + } + }, + "required": [ + "mao", + "summary" + ], + "type": "object" +}
2 tool updates
- Changed
pull_comps8 fields changed- removed
Input schema / properties / addressRemoved value: -{ - "description": "Subject property address.", - "type": "string" -} - added
Input schema / properties / cityAdded value: +{ + "type": "string" +} - added
Input schema / properties / rentCountAdded value: +{ + "description": "Rental comps to return (default 10).", + "type": "number" +} - added
Input schema / properties / saleCountAdded value: +{ + "description": "Comparable sales to return (default 10).", + "type": "number" +} - added
Input schema / properties / stateAdded value: +{ + "description": "Two-letter state, e.g. \"MN\".", + "type": "string" +} - added
Input schema / properties / streetAdded value: +{ + "description": "Street address incl. house number, e.g. \"812 7th St SE\".", + "type": "string" +} - added
Input schema / properties / zipAdded value: +{ + "type": "string" +} - changed
Input schema / requiredPrevious value: -[ - "address" -]New value: +[ + "street", + "city", + "state" +]
- Changed
str_market_data7 fields changed- removed
Input schema / properties / addressRemoved value: -{ - "description": "Location or subject address.", - "type": "string" -} - added
Input schema / properties / bathsAdded value: +{ + "type": "number" +} - added
Input schema / properties / bedroomsAdded value: +{ + "description": "Bedrooms filter (default 2).", + "type": "number" +} - added
Input schema / properties / guestsAdded value: +{ + "type": "number" +} - added
Input schema / properties / latitudeAdded value: +{ + "type": "number" +} - added
Input schema / properties / longitudeAdded value: +{ + "type": "number" +} - changed
Input schema / requiredPrevious value: -[ - "address" -]New value: +[ + "latitude", + "longitude" +]
6 tool updates
- First observed
analyze_deal - First observed
best_use - First observed
list_strategies - First observed
pull_comps - First observed
solve_max_offer - First observed
str_market_data
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Deterministic real estate underwriting, deal analysis & reports: Fix & Flip, BRRRR, construction.
Real estate deal analysis from chat: rental underwriting, buy-box matching, deal library, docs.
- mcpOAuthcom.hotelvalora
Institutional hotel valuations in seconds: NOI/cap rate, USALI P&L, IRR/MOIC, markets, compsets.
Search real-estate deals, rank top areas, run rental/BRRRR/flip analysis, pull sold comps.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceA headless MCP connector that lets you underwrite commercial and multifamily deals inside a Claude chat, providing exact arithmetic for NOI, valuation, debt sizing, DSCR, and returns.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to find vetted, daily-scored US residential real-estate investment deals with pay-per-request via USDC on Base.15MIT
- FlicenseNot gradedqualityBmaintenanceProvides free property and parcel intelligence using official US government data APIs, county assessor records, and live listings, with tools for hazard risk checks, affordability calculations, and parcel ranking.-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.6/5.0
Disambiguation5/5
Each tool targets a distinct analytical task: analyzing a specific strategy, comparing strategies, listing strategy metadata, and reverse-solving an offer. No two tools overlap in purpose.
Naming Consistency4/5
Three tools follow the verb_noun pattern (analyze_deal, list_strategies, solve_max_offer), but 'best_use' is an adjective_noun phrase, breaking the consistency. This is a minor deviation.
Tool Count5/5
With 4 tools, the set is well-scoped for a real estate analysis server, covering core workflows without unnecessary redundancy.
Completeness5/5
The set covers the essential lifecycle: understanding strategies, evaluating a deal, finding the best strategy, and calculating max offer. No obvious gaps for the stated domain.