Skip to main content
Glama
Sign In
FinPilot AI

FinPilot AI

by ShahzaadAhmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

analyze_portfolio_diversification

Assess stock portfolio diversification by sector and asset class to identify concentration risks and balance your investments.

Instructions

Analyze the sector and asset class diversification of a given stock portfolio.

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": {
      "holdings": "<holdings>"
    },
    "name": "analyze_portfolio_diversification"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdingsYesArray of portfolio holdings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose return format, side effects, data sensitivity, or operational behavior (e.g., read-only nature, output structure). For a tool that performs analysis, 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 redundant information. It is front-loaded with the verb and resource, making it easy to parse.

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?

Given the tool's simplicity (one parameter), the description is minimally adequate. However, with no output schema and no behavioral notes, the agent cannot know what the analysis returns or how to interpret results, leaving a notable gap in completeness.

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 fully documents the 'holdings' parameter, so schema coverage is 100%. The description adds no additional meaning beyond the schema; it simply restates the overall purpose. Baseline 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 states a specific verb ('Analyze') and resource ('sector and asset class diversification of a given stock portfolio'). This distinguishes it from siblings like get_risk_assessment (risk) or generate_investment_report (broader report).

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 provides no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The agent must infer usage solely from the name and description, which is ambiguous relative to related sibling tools.

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