Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

alphaIntelligence_newsSentiments

Fetch market news and sentiment data for specific stocks, crypto, or forex symbols, filtered by topics and time periods to analyze financial market sentiment.

Instructions

Fetches market news and sentiment data from Alpha Vantage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickersListNoList of stock/crypto/forex symbols (e.g., ["AAPL", "GOOGL"]).
topicsNoSpecific topics to filter news for (e.g., "technology", "earnings").
time_fromNoStart time for news articles (YYYYMMDDTHHMM format).
time_toNoEnd time for news articles (YYYYMMDDTHHMM format).
sortNoSort order for results.LATEST
limitNoNumber of results to return (1-1000).

Implementation Reference

  • Core handler function that executes all AVantage-based MCP tools, including alphaIntelligence_newsSentiments. Manages API key resolution, AVantage client lifecycle via resourceManager, invokes the specific library method, handles 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}`
        );
      }
    }
  • Zod schema defining the input parameters for the alphaIntelligence_newsSentiments tool, including optional tickers, topics, time range, sort order, and limit.
    export const NewsSentimentsParamsSchema = z.object({
      tickersList: z.array(z.string()).optional().describe('List of stock/crypto/forex symbols (e.g., ["AAPL", "GOOGL"]).'),
      topics: z.string().optional().describe('Specific topics to filter news for (e.g., "technology", "earnings").'),
      time_from: z.string().optional().describe('Start time for news articles (YYYYMMDDTHHMM format).'),
      time_to: z.string().optional().describe('End time for news articles (YYYYMMDDTHHMM format).'),
      sort: z.enum(['LATEST', 'EARLIEST', 'RELEVANCE']).default('LATEST').optional().describe('Sort order for results.'),
      limit: z.number().int().min(1).max(1000).default(50).optional().describe('Number of results to return (1-1000).'),
    }).describe('Parameters for fetching market news and sentiment data.')
  • src/index.ts:121-136 (registration)
    Registers the MCP tool 'alphaIntelligence_newsSentiments' on the FastMCP server, linking the schema, description, and specific execution logic that calls the AVantage library's newsSentiments method via the generic handler.
    // --- Alpha Intelligence Tools ---
    server.addTool({
      name: "alphaIntelligence_newsSentiments",
      description: "Fetches market news and sentiment data from Alpha Vantage.",
      parameters: schemas.NewsSentimentsParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "alphaIntelligence_newsSentiments",
          args,
          context,
          (av, params) => av.alphaIntelligence.newsSentiments(params)
        ),
    });
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 states what the tool does but doesn't describe how it behaves: there's no information about rate limits, authentication requirements, error handling, response format, or whether it's a read-only operation (though 'fetches' implies reading). For a tool with no annotations, 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 a single, clear sentence that efficiently communicates the core functionality without unnecessary words. It's appropriately sized and front-loaded, with every word earning its place. There's no redundancy or structural issues.

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 tool's complexity (6 parameters, no output schema, no annotations), the description is insufficiently complete. It doesn't explain what the output looks like (news articles with sentiment scores?), how results are structured, or any limitations (e.g., data freshness, source reliability). With no output schema and no annotations, the description should provide more context about the tool's behavior and results.

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 schema description coverage is 100%, with all parameters well-documented in the input schema. The description doesn't add any parameter-specific information beyond what's already in the schema (e.g., it doesn't explain relationships between parameters like 'tickersList' and 'topics'). According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 ('market news and sentiment data from Alpha Vantage'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from its many siblings (e.g., other Alpha Intelligence tools like 'insiderTransactions' or 'topGainersLosers'), which would require a 5. The description is specific but lacks sibling comparison.

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. With numerous sibling tools available (e.g., for commodities, forex, technical indicators), there's no indication of when news and sentiment data is appropriate versus other data types. It mentions the data source but not the use case context, leaving the agent to infer usage scenarios.

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