FinPilot AI

email_investment_report

Email investment reports to specified addresses. Provide the ticker and report content to deliver analysis directly to recipients.

Instructions

Emails an investment report to a specified address.

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": {
      "emailAddress": "<emailAddress>",
      "ticker": "<ticker>",
      "reportContent": "<reportContent>"
    },
    "name": "email_investment_report"
  }
}

Input Schema

Name	Required	Description
`ticker`	Yes	The stock ticker symbol
`emailAddress`	Yes	The recipient email address
`reportContent`	Yes	The full text or summary of the report to email

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 1, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states that an email is sent, without detailing any side effects, permissions required, delivery guarantees, or error behavior. For a side-effecting action like sending email, this is a significant gap.

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, concise sentence with no redundancy, front-loading the verb and core purpose. Every word earns its place, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with fully documented parameters, the description is minimally viable. However, it omits any context about prerequisites (e.g., whether a report must already exist), connection to sibling tools, or expected outcomes, which would be helpful given the absence of annotations and output schema.

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?

The input schema already describes all three parameters (ticker, emailAddress, reportContent) with 100% coverage. The description adds no additional parameter-level meaning, so it meets the baseline but does not enhance understanding beyond the 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 clearly states the action ('Emails') and the object ('an investment report'), with a recipient address specified. This unambiguously distinguishes it from sibling tools like generate_investment_report, which creates reports rather than sends them.

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

Usage Guidelines2/5

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

The description offers no guidance on when to use this tool versus alternatives. It does not mention that a report should be generated first (e.g., via generate_investment_report) or any scenario where this tool is the appropriate choice, leaving the agent to infer usage entirely.

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

Deploy Server