Skip to main content
Glama

USDV Capital — Your Real Estate CFO

by io.github.USDVCapital

action-send_report

Send a professionally formatted Capital Advisory Report (PDF) to an investor's email. Use after running any calculator tool. Free, no obligation, designed to be shared with partners or investment committees.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesRecipient's real email address as 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.
locationNoLocation context
reportTypeYesReport type: dscr_analysis, flip_roi, rental_cashflow, str_revenue, brrrr_analysis, construction_budget, deal_analysis
investorNameNoName to personalize the report
calculationDataYesOutput from the calculator tool

TDQS

A4.2/5.0
Behavior4/5

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

The description reveals the primary side effect (sending an email) and adds context beyond annotations (PDF format, free, no obligation, designed for sharing). Annotations declare readOnlyHint=false, so the agent already knows this is a write action; the description supplements with relevant behavioral details.

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 sentences, front-loaded with the main action, and contains no redundant information. Every sentence adds value (purpose and usage context).

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 5 parameters, nested object, and no output schema, the description is brief but supported by rich schema descriptions. It explains when to use the tool and the main action, though it does not detail return values. However, the schema and annotations cover most of the needed context.

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 description coverage is 100%, so the schema fully documents parameters. The description does not add any parameter-specific meaning beyond what schema already provides, but the baseline of 3 is appropriate due to high coverage.

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 specific verb 'Send' and the resource 'a professionally formatted Capital Advisory Report (PDF) to an investor's email'. It distinguishes from sibling calculator tools by focusing on the action of sending a report rather than computing data.

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?

Explicitly states 'Use after running any calculator tool', which is a clear precondition for usage. It does not mention when not to use or alternatives, but the context is sufficient for tool selection.

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 toolsInspect
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