USDV Capital — Your Real Estate CFO

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>",
      "reportType": "<reportType>",
      "calculationData": "<calculationData>"
    },
    "name": "action-send_report"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	Recipient'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.
`location`	No	Location context
`reportType`	Yes	Report type: dscr_analysis, flip_roi, rental_cashflow, str_revenue, brrrr_analysis, construction_budget, deal_analysis
`investorName`	No	Name to personalize the report
`calculationData`	Yes	Output from the calculator tool

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedMay 21, 2026

changedInput schema / properties / email / description

Previous value: -"Email address"New value: +"Recipient'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."

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

addedInput schema / properties / email / 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.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 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?