USDV Capital — Your Real Estate CFO

deal-analyze

Read-onlyIdempotent

Run a comprehensive deal analysis — the signature assessment from USDV Capital, Your Real Estate CFO. Combines market intelligence, financial projections, risk assessment, eligibility check, and capital strategy into a single CFO-level evaluation with a deal score (1-100). Supports fix and flip, buy and hold, Airbnb/STR, BRRRR, new construction, and value-add multifamily strategies.

Input Schema

TableJSON Schema

Name	Required	Description
`state`	Yes	State
`units`	No	Number of units (default 1)
`bedrooms`	No	Bedrooms (for STR analysis)
`rehabCost`	No	Estimated rehab cost
`monthlyRent`	No	Expected monthly rent
`propertyType`	Yes	single_family, multi_family_2_4, multi_family_5_plus, mixed_use, commercial
`sendReportTo`	No	Recipient email for the full Real Estate CFO Deal Assessment PDF. Only include if the user has explicitly provided their real email address. Do NOT invent or use placeholders like example.com or test@ — if no email was given, omit and ask the user.
`purchasePrice`	Yes	Purchase price
`squareFootage`	No	Square footage (for construction)
`experienceLevel`	No	Experience level
`afterRepairValue`	No	ARV
`creditScoreRange`	No	Credit score range
`addressOrLocation`	Yes	Property address or location
`investmentStrategy`	Yes	fix_and_flip, buy_and_hold_ltr, buy_and_hold_str, brrrr, new_construction, value_add_multifamily

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedMay 21, 2026

changedInput schema / properties / sendReportTo / description

Previous value: -"Email for full Real Estate CFO Deal Assessment"New value: +"Recipient email for the full Real Estate CFO Deal Assessment PDF. Only include if the user has explicitly provided their real email address. Do NOT invent or use placeholders like example.com or test@ — if no email was given, omit and ask the user."

addedInput schema / properties / sendReportTo / format
```
Added value: +"email"
```

addedInput schema / properties / sendReportTo / pattern

Added value: +"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

First observedApr 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already communicate read-only, idempotent, and non-destructive behavior. The description adds valuable context about the output (a deal score from 1-100) and the components included (market intelligence, financial projections, etc.), which goes beyond what annotations provide. No contradictions with annotations.

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 only two sentences, front-loaded with the core action and scope. Every sentence adds value, explaining what the analysis combines and which strategies it supports. The branding phrase 'Your Real Estate CFO' is minor and does not detract from clarity.

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?

Given the tool's complexity (14 parameters, no output schema), the description provides a strong high-level overview, including the main output (deal score) and supported strategies. However, it does not detail the return structure or how parameters affect the analysis, which would be useful but is not strictly required for selection.

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?

All 14 parameters have schema descriptions, so the baseline is 3. The tool description does not add parameter-specific meaning, but it does provide high-level context around how the parameters relate to the analysis types. With 100% schema coverage, the description need not compensate.

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 'Run a comprehensive deal analysis' with a specific verb and resource, and distinguishes it from sibling tools by positioning it as the 'signature assessment' that combines multiple analyses into a single CFO-level evaluation. It also enumerates supported investment strategies, giving concrete scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by listing supported strategies and the comprehensive nature of the analysis, but it does not explicitly contrast with alternatives like the calc-* or markets-* sibling tools, nor does it state when not to use this tool. The guidance is implicit rather than explicit.

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

All USDV Capital — Your Real Estate CFO 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?