Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

optionsData_historicalOptions

Retrieve historical options chain data for specific stocks and dates to analyze past market conditions and trading patterns.

Instructions

Fetches historical options chain data. Premium endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesThe underlying stock symbol (e.g., "AAPL").
dateNoSpecific date (YYYY-MM-DD) for historical data.
datatypeNoData format for the response.json

Implementation Reference

  • src/index.ts:965-979 (registration)
    Registers the MCP tool 'optionsData_historicalOptions' with name, description, input schema, and an inline execute handler that calls the shared executeAvantageTool helper with the specific Avantage library method.
    server.addTool({
      name: "optionsData_historicalOptions",
      description: "Fetches historical options chain data. Premium endpoint.",
      parameters: schemas.OptionsDataHistoricalOptionsParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "optionsData_historicalOptions",
          args,
          context,
          (av, params) => av.optionsData.historicalOptions(params)
        ),
    });
  • Zod schema defining the input parameters for the tool: required 'symbol', optional 'date' and 'datatype'.
    export const OptionsDataHistoricalOptionsParamsSchema = z.object({
      symbol: z.string().describe('The underlying stock symbol (e.g., "AAPL").'),
      date: z.string().optional().describe('Specific date (YYYY-MM-DD) for historical data.'),
      datatype: DatatypeSchema.default('json').optional(),
    }).describe('Parameters for fetching historical options chain data (Premium).')
  • Shared handler logic executed by this tool (and all others): resolves API key, gets/manages AVantage client instance, invokes the library method av.optionsData.historicalOptions(params), handles errors, returns JSON string of 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Premium endpoint,' which suggests potential authentication or rate-limiting needs, but doesn't detail these aspects, response format, error handling, or data scope. This leaves significant gaps for a data-fetching tool.

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 with two short sentences that are front-loaded and waste no words. Every part ('Fetches historical options chain data. Premium endpoint.') earns its place by stating purpose and a key behavioral note.

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 (fetching financial data with 3 parameters) and lack of annotations and output schema, the description is incomplete. It doesn't explain return values, error cases, or detailed behavioral traits, 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.

Parameters3/5

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

The input schema has 100% description coverage, thoroughly documenting all parameters. The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline of 3 without compensating for any gaps.

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 verb ('fetches') and resource ('historical options chain data'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from its sibling 'optionsData_realtimeOptions' beyond the 'historical' qualifier, which is implied but not contrasted.

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 like 'optionsData_realtimeOptions' or other data-fetching tools. The mention of 'Premium endpoint' hints at potential access restrictions but doesn't clarify usage context or prerequisites.

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