Skip to main content
Glama
darved2305

groww-mcp

by darved2305

get_portfolio_summary

Retrieve a summary of your investment portfolio showing total invested amount, current value, profit/loss, and daily performance.

Instructions

Total invested, current value, total P&L, day's P&L

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool registration and handler implementation for "get_portfolio_summary". It calls growwClient.getPortfolioSummary() and formats the output.
    // ── get_portfolio_summary ─────────────────────────────────
    server.tool(
      "get_portfolio_summary",
      "Total invested, current value, total P&L, day's P&L",
      {},
      async () => {
        try {
          const s = await growwClient.getPortfolioSummary();
          const text = [
            `💼 PORTFOLIO SUMMARY`,
            `${"─".repeat(40)}`,
            `Invested:      ${formatCurrency(s.totalInvested)}`,
            `Current Value:  ${formatCurrency(s.currentValue)}`,
            `Total P&L:     ${pnlSign(s.totalPnl)} (${formatPercent(s.totalPnlPercent)})`,
            `Day's P&L:     ${pnlSign(s.dayPnl)} (${formatPercent(s.dayPnlPercent)})`,
            `Holdings:      ${s.holdingsCount} stocks`,
            ``,
            `As of ${nowIST()}`,
          ].join("\n");
          return mcpText(text);
        } catch (err) {
          return mcpError(normalizeError(err));
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions metrics but doesn't disclose behavioral traits such as whether it's a read-only operation, requires authentication, has rate limits, or how data is sourced (e.g., real-time vs. delayed). This leaves gaps in understanding the tool's behavior.

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 very concise, listing key metrics in a single phrase without unnecessary words. However, it could be more structured by front-loading the purpose (e.g., 'Retrieve a summary of portfolio metrics including...') to improve clarity.

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 complexity of financial portfolio tools and lack of annotations or output schema, the description is incomplete. It lists metrics but doesn't explain return values, data formats, or potential errors, leaving the agent with insufficient context for reliable use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but this is acceptable given the lack of parameters, aligning with the baseline for zero parameters.

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

Purpose3/5

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

The description lists specific metrics (total invested, current value, total P&L, day's P&L) which implies it retrieves portfolio summary data, but it lacks a clear verb and doesn't distinguish from sibling tools like get_holdings or get_positions. It's vague about what exactly 'portfolio summary' entails beyond the listed metrics.

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 on when to use this tool versus alternatives like get_holdings or get_positions, which might offer more detailed or different portfolio information. The description only states what metrics are returned, not the context for selection.

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/darved2305/groww-mcp'

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