USDV Capital — Your Real Estate CFO

action-consultation

Schedule a free consultation with a USDV Capital Capital Advisor. 15-30 minutes via phone or video. No obligation, no credit check. Your Capital Advisor will review deal details before the call.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	Yes	Real email address provided by the user. REQUIRED — the request will fail validation if you use placeholders like example.com, test@, or 'not_provided'. Ask the user for it before calling this tool.
`phone`	Yes	Real phone number provided by the user. Ask the user before calling this tool.
`topic`	No	What to discuss
`lastName`	Yes	Last name as provided by the user.
`firstName`	Yes	First name as provided by the user.
`dealDetails`	No	Deal details for advisor preparation
`preferredDate`	No	Preferred date (ISO format)
`preferredTime`	No	morning, afternoon, evening

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate non-read-only, non-idempotent, open-world behavior. The description adds context that the advisor reviews deal details before the call, providing insight into what happens upon invocation. 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?

Three sentences, about 40 words, front-loaded with the main purpose. Every sentence earns its place: purpose, logistics, and advisor preparation. No redundancy.

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 simple scheduling tool, the description fully covers the workflow: scheduling, duration, method, and advisor preparation. With schema handling parameter details and no output schema, this is sufficient for an agent to invoke correctly.

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 covers 100% of parameters with descriptive text, so baseline is 3. The description reinforces the dealDetails purpose but does not add new parameter semantics beyond what the schema provides.

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?

Description states 'Schedule a free consultation with a USDV Capital Capital Advisor' – a specific verb and resource that clearly distinguishes it from sibling action tools like action-prequalify. It also provides logistics (15-30 minutes, phone/video) that further define the tool's purpose.

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: free consultation, no obligation, no credit check, and advisor preparation. However, it does not explicitly mention alternatives or when not to use, so it stops short of full when/when-not guidance.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, especially the calculators and utilities. The markets-* group has five tools that all return market data, but each has a distinct focus (compare, nearby, screener, search, stats) with descriptions that clarify the differences. Overall, an agent can generally tell them apart, though the market tools could still cause minor confusion.

Naming Consistency4/5

The naming convention is consistent across categories using lowercase with hyphens and a prefix (action-, calc-, deal-, eligibility-, markets-, util-). Within categories there is slight inconsistency, such as action-consultation (noun) vs action-prequalify (verb) vs action-send_report (verb_noun), but the overall pattern is predictable and readable.

Tool Count4/5

With 23 tools, the server covers a broad range of real estate CFO services: property analysis, market intelligence, eligibility, and client actions. This is slightly on the heavy side but each tool serves a distinct purpose within the domain. It could be trimmed, but the count is not unreasonable given the scope.

Completeness4/5

The tool set covers the core lifecycle of a real estate deal: market research, property-level analysis, calculators for various strategies, eligibility checking, and client engagement actions. Minor gaps exist—such as no tool for tracking existing deals or a general mortgage payment calculator—but the main workflows are well supported. Completeness is strong for the stated purpose.

Resources

Need Help?