Skip to main content
Glama
Sign In
FinPilot AI

FinPilot AI

by ShahzaadAhmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

orchestrate_financial_analysis

Answer investment questions by coordinating market data, financials, and valuation agents to deliver a unified stock analysis.

Instructions

Coordinates multiple agents (Market Data, Financials, Valuation) to produce a unified analysis of a stock.

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": {
      "query": "<query>",
      "ticker": "<ticker>"
    },
    "name": "orchestrate_financial_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe natural language question from the user (e.g. "Is AAPL a good buy right now?")
tickerYesThe target ticker symbol extracted from the query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only mentions coordination of multiple agents, but does not state whether the operation is read-only, describe potential side effects, error handling, or output format. For an orchestration tool, this is insufficient transparency without annotation safety hints.

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 sentence, front-loaded with the key verb 'Coordinates,' and contains no redundant or extraneous information. It is highly concise and well-structured.

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

Completeness2/5

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

Given the tool's orchestration complexity, the description is under-specified: it lacks details on expected output (though 'unified analysis' hints at it), potential latency, failure modes, or whether it is appropriate for all analysis requests. The absence of an output schema further increases the need for descriptive completeness, which is not met.

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%, with both query and ticker fully described. The tool description adds no additional parameter-specific meaning beyond contextualizing that these inputs feed a multi-agent analysis, so the baseline of 3 is appropriate.

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 specifies the tool's function: coordinating multiple analytical agents (Market Data, Financials, Valuation) to produce a unified stock analysis. This distinguishes it from sibling tools that perform individual lookups or report generation, establishing a unique purpose.

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

Usage Guidelines3/5

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

The description implies usage for comprehensive analysis requests ('coordinates multiple agents... produce a unified analysis'), but it does not explicitly state when to use this tool versus alternatives. No exclusions or when-not-to-use guidance is provided, leaving the conditions for selection somewhat implied rather than explicit.

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

Deploy Server

Other Tools