Skip to main content
Glama
darved2305

groww-mcp

by darved2305

search_funds

Find mutual funds by name, category, or asset management company to support investment decisions on Groww.

Instructions

Search mutual funds by name, category, or AMC

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query — fund name, category, or AMC
categoryNoFilter by category, e.g. Large Cap, Flexi Cap
amcNoFilter by AMC, e.g. Axis, Mirae, SBI

Implementation Reference

  • Tool registration and handler logic for "search_funds". It uses `growwClient.searchFunds` to fetch data and formats the output for the MCP client.
    server.tool(
      "search_funds",
      "Search mutual funds by name, category, or AMC",
      {
        query: z.string().describe("Search query — fund name, category, or AMC"),
        category: z.string().optional().describe("Filter by category, e.g. Large Cap, Flexi Cap"),
        amc: z.string().optional().describe("Filter by AMC, e.g. Axis, Mirae, SBI"),
      },
      async ({ query, category, amc }) => {
        try {
          const results = await growwClient.searchFunds(query, category, amc);
          if (results.length === 0) return mcpText(`🔍 No mutual funds found for "${query}"`);
    
          const lines = results.map((f, i) => {
            const stars = "⭐".repeat(Math.min(f.rating, 5));
            return [
              `${i + 1}. ${f.name}`,
              `   AMC: ${f.amc}  |  Category: ${f.category}`,
              `   NAV: ${formatCurrencyExact(f.nav)}  |  1Y Returns: ${formatPercent(f.returns1y)}`,
              `   Rating: ${stars}  |  ISIN: ${f.isin}`,
            ].join("\n");
          });
    
          const text = [`🔍 FUND SEARCH: "${query}" — ${results.length} results`, `${"─".repeat(55)}`, ...lines].join("\n\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 the full burden. It states the search functionality but doesn't disclose behavioral traits such as whether this is a read-only operation, how results are returned (e.g., pagination, sorting), rate limits, or authentication requirements. This is a significant gap for a search tool with no annotation coverage.

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, efficient sentence with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list of funds, detailed results), how to interpret results, or any behavioral context like error handling. For a search tool with 3 parameters and no structured output, more guidance is needed.

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 schema already documents all parameters thoroughly. The description adds minimal value by listing the searchable fields (name, category, AMC), which aligns with the schema but doesn't provide additional syntax or format details beyond what's in the schema descriptions.

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 clearly states the tool's purpose as searching mutual funds by specific criteria (name, category, or AMC), which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'search_stocks' or 'get_fund_details' beyond the mutual fund focus.

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. The description doesn't mention sibling tools like 'search_stocks' for different asset types or 'get_fund_details' for detailed information, nor does it specify prerequisites or exclusions for usage.

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