Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

fundamentalData_incomeStatement

Retrieve annual or quarterly income statement data for stocks to analyze financial performance and profitability metrics.

Instructions

Fetches income statement data (annual/quarterly). Premium endpoint.

Input Schema

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

Implementation Reference

  • src/index.ts:837-852 (registration)
    Registration of the 'fundamentalData_incomeStatement' MCP tool. Specifies the tool name, description, input parameters schema, and an execute handler that invokes the shared 'executeAvantageTool' wrapper to call the AVantage library's 'incomeStatement' method.
    server.addTool({
      name: "fundamentalData_incomeStatement",
      description:
        "Fetches income statement data (annual/quarterly). Premium endpoint.",
      parameters: schemas.FundamentalDataSymbolParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "fundamentalData_incomeStatement",
          args,
          context,
          (av, params) => av.fundamentalData.incomeStatement(params.symbol)
        ),
    });
  • Zod input schema for the tool, defining a single required 'symbol' parameter (stock ticker). 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.')
  • Shared generic handler function that implements the core execution logic for the 'fundamentalData_incomeStatement' tool (and similar tools). Manages AVantage client instance, performs the API call via the provided method, handles authentication/errors, and returns JSON data.
    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}`
        );
      }
    }
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 of behavioral disclosure. It mentions 'Premium endpoint,' which implies potential access restrictions or costs, but lacks details on rate limits, authentication needs, data formats, or error handling. This leaves significant gaps for a tool that fetches financial data.

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 concise and front-loaded, stating the core functionality in a single sentence. However, it could be more structured by separating the premium endpoint note for clarity, but it remains efficient with no wasted words.

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 fetching financial data, no annotations, and no output schema, the description is incomplete. It lacks details on return values (e.g., data structure, fields), error cases, or behavioral traits like pagination or caching, making it inadequate for full agent understanding.

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 has 100% description coverage, with the parameter 'symbol' clearly documented. The description does not add any additional meaning beyond the schema, such as explaining symbol formats or constraints, so it meets the baseline for high schema coverage without extra value.

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 fetching income statement data with annual/quarterly frequency, which is a specific verb (fetches) and resource (income statement data). It distinguishes from siblings like fundamentalData_balanceSheet or fundamentalData_cashFlow by specifying the type of financial statement, though it does not explicitly contrast with them.

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, such as other fundamental data tools like fundamentalData_balanceSheet or fundamentalData_cashFlow. It mentions it is a 'Premium endpoint,' which hints at access restrictions but does not specify usage contexts or exclusions.

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