FinPilot AI

generate_investment_report

Aggregates market findings and recommendations into a structured investment report, enabling informed decision-making.

Instructions

Aggregates findings into a comprehensive AI investment report.

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": {
      "ticker": "<ticker>",
      "summary": "<summary>",
      "recommendation": "<recommendation>"
    },
    "name": "generate_investment_report"
  }
}

Input Schema

Name	Required	Description
`ticker`	Yes	The stock ticker symbol
`summary`	Yes	Executive summary text
`recommendation`	Yes	Final investment recommendation

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 1, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It states the tool aggregates findings but doesn't specify whether it is a pure function, persistence side effects, authentication requirements, or output format. This lack of context is a significant gap for a generation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence without extraneous words. It's appropriately concise, though it could include more detail without becoming bloated.

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?

The tool has simple parameters and full schema coverage, but no output schema and no annotations. The description leaves ambiguity about what the report contains or how it's delivered. For a low-complexity tool, it's minimally adequate but not complete.

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 baseline is 3. The description doesn't add any parameter-specific meaning beyond what the schema already provides, but it doesn't need to given full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'aggregates' and resource 'AI investment report,' clearly indicating the tool creates a report. However, it doesn't differentiate from siblings like email_investment_report or orchestrate_financial_analysis, so it lacks sibling distinction.

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?

No guidance is provided about when to use this tool versus the sibling tools. The description doesn't mention prerequisites, alternative tools, or exclusions.

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

Deploy Server