Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

fundamentalData_cashFlow

Retrieve cash flow statements for stocks to analyze financial health and liquidity. Provides annual and quarterly data for investment research and financial analysis.

Instructions

Fetches cash flow data (annual/quarterly). Premium endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesThe stock symbol (e.g., "IBM").

Implementation Reference

  • Generic execution handler for all MCP tools, including 'fundamentalData_cashFlow'. Manages authentication, AVantage client lifecycle via resourceManager, invokes the specific library method (av.fundamentalData.cashFlow), and returns JSON-stringified data or throws UserError on failure.
    async function executeAvantageTool<TArgs, TResult>(
      toolName: string,
      args: TArgs,
      context: Context<Record<string, unknown> | undefined>, // Use the imported Context type directly
      avantageMethod: (
        av: AVantage,
        args: TArgs
      ) => Promise<{ error?: boolean; reason?: string; data?: TResult }>
    ): Promise<string> {
      logger.info(`Executing '${toolName}' tool for request ID: ${context}`);
      logger.debug(`Args for ${toolName}: ${JSON.stringify(args)}`);
    
      // --- Authentication & Resource Management ---
      // Access extraArgs safely - it might be null or undefined
      const extraArgsApiKey = context.extraArgs?.apiKey as string | undefined;
      const apiKey = extraArgsApiKey || config.apiKey;
    
      if (!apiKey) {
        logger.error(`'${toolName}' failed: Alpha Vantage API key missing.`);
        throw new UserError(apiKeyErrorMessage);
      }
      logger.debug(
        `Using AV API key (source: ${extraArgsApiKey ? "extraArgs" : "environment"}) for ${toolName}`
      );
    
      try {
        // Get or create AVantage instance managed by ResourceManager
        const av = await resourceManager.getResource<AVantage>(
          apiKey, // Cache key is the resolved API key
          "avantage_client", // Type identifier for logging
          async (key) => {
            // Factory Function
            logger.info(
              `Creating new AVantage instance for key ending ...${key.slice(-4)}`
            );
            // AVantage library reads AV_PREMIUM from process.env internally
            return new AVantage(key);
          },
          async (avInstance) => {
            // Cleanup Function (no-op needed for AVantage)
            logger.debug(`Destroying AVantage instance (no-op)`);
          }
        );
    
        // --- Library Call ---
        const result = await avantageMethod(av, args);
    
        // --- Response Handling ---
        if (result.error) {
          logger.warn(
            `'${toolName}' failed. Reason from avantage: ${result.reason}`
          );
          throw new UserError(result.reason || `Tool '${toolName}' failed.`);
        }
    
        if (result.data === undefined || result.data === null) {
          logger.warn(`'${toolName}' completed successfully but returned no data.`);
          return "null"; // Return string "null" for empty data
        }
    
        logger.info(`'${toolName}' completed successfully.`);
        // Stringify the data part of the response
        return JSON.stringify(result.data);
      } catch (error: any) {
        logger.error(
          `Error during execution of '${toolName}': ${error.message}`,
          error
        );
        // If it's already a UserError, rethrow it
        if (error instanceof UserError) {
          throw error;
        }
        // Otherwise, wrap it in a UserError
        throw new UserError(
          `An unexpected error occurred while executing tool '${toolName}': ${error.message}`
        );
      }
    }
  • Zod schema defining input parameters for the 'fundamentalData_cashFlow' tool: requires a 'symbol' string (e.g., 'IBM'). Used for input validation.
    export const FundamentalDataSymbolParamsSchema = z.object({
      symbol: z.string().describe('The stock symbol (e.g., "IBM").'),
    }).describe('Parameter schema requiring only a stock symbol.')
  • src/index.ts:871-885 (registration)
    Registers the 'fundamentalData_cashFlow' MCP tool with FastMCP server, linking name, description, input schema, and execute handler that delegates to generic executeAvantageTool with specific library call.
    server.addTool({
      name: "fundamentalData_cashFlow",
      description: "Fetches cash flow data (annual/quarterly). Premium endpoint.",
      parameters: schemas.FundamentalDataSymbolParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "fundamentalData_cashFlow",
          args,
          context,
          (av, params) => av.fundamentalData.cashFlow(params.symbol)
        ),
    });
  • Specific callback passed to executeAvantageTool that invokes the Alpha Vantage library's cashFlow method with the validated symbol parameter.
          (av, params) => av.fundamentalData.cashFlow(params.symbol)
        ),
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'Premium endpoint' which hints at potential access restrictions or costs, but doesn't describe authentication requirements, rate limits, data freshness, pagination, error conditions, or what 'fetches' actually returns. For a financial data tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise - just 7 words in a single sentence. Every word earns its place: 'Fetches' (action), 'cash flow data' (resource), '(annual/quarterly)' (key specification), 'Premium endpoint' (important constraint). No wasted words or redundant information.

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 financial data tool with no annotations and no output schema, the description is insufficient. It doesn't explain what format the cash flow data returns (structured financial statements? raw numbers?), doesn't specify time periods available, doesn't mention authentication or rate limiting, and doesn't clarify what 'Premium endpoint' means operationally. The agent would struggle to use this effectively without trial and error.

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 only one parameter (symbol) fully documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides about the symbol parameter. Baseline 3 is appropriate when the schema does the heavy lifting for parameter documentation.

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 action ('fetches') and resource ('cash flow data') with specificity about the data type and periodicity (annual/quarterly). It distinguishes from some siblings like fundamentalData_balanceSheet or fundamentalData_incomeStatement by focusing on cash flow, but doesn't explicitly differentiate from all financial data tools.

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 retrieving cash flow statements rather than other financial statements, but doesn't provide explicit guidance on when to choose this over alternatives like fundamentalData_balanceSheet or fundamentalData_incomeStatement. The 'Premium endpoint' note suggests potential access restrictions but doesn't specify when to use premium vs free endpoints.

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/MissionSquad/mcp-avantage'

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