Skip to main content
Glama
coolksrini

finpilot-mcp

by coolksrini

analyze_portfolio

Analyze investment portfolios by processing CAS PDF files or direct data inputs to provide comprehensive financial insights.

Instructions

Analyze investment portfolio from a CAS PDF or direct data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dobNoDate of birth in DDMMYYYY format — used alongside PAN to infer the password.
panNoPAN number — used to auto-infer the password if not provided (CAMS/NSDL/CDSL CAS PDFs are often protected with DOB in DDMMYYYY format).
passwordNoPDF password if the file is password-protected.
file_pathNoPath or URL to the CAS PDF (NSDL/CDSL/CAMS consolidated statement). Local path: /Users/name/Downloads/cas_statement.pdf Cloud URL: https://drive.google.com/... or https://1drv.ms/... (must be shared with "anyone with link can view")
portfolio_dataNoDirect portfolio data as a dict (alternative to PDF)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided, so the description carries full burden. It only states 'analyze' without disclosing behavior (e.g., read-only, side effects, authentication needs), return format, or processing 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?

Single sentence, zero waste. Perfectly concise for the information it conveys.

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?

For a tool with five parameters and an output schema, the description is too brief. It lacks context on output, workflow, or prerequisites, making it insufficient for an agent to fully understand invocations.

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 coverage is 100% with detailed parameter descriptions. The tool description adds minimal context (PDF vs direct data) but does not deepen understanding beyond what the schema provides.

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 tool's purpose: 'Analyze investment portfolio from a CAS PDF or direct data.' It specifies the verb (analyze), resource (investment portfolio), and source options, distinguishing it from sibling tools.

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 on when to use this tool versus alternatives or when to choose PDF vs direct data. Siblings are tangentially related (credit health, loans) but no explicit differentiation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/coolksrini/finpilot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server