Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

optionsData_realtimeOptions

Fetch real-time options chain data for specific stock symbols to analyze market positions and make informed trading decisions.

Instructions

Fetches realtime options chain data. Premium endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesThe underlying stock symbol (e.g., "AAPL").
contractNoSpecific option contract ID to fetch details for.
datatypeNoData format for the response.json

Implementation Reference

  • src/index.ts:949-963 (registration)
    Registers the MCP tool 'optionsData_realtimeOptions' with server.addTool, defining its name, description, input schema, and execute handler function.
    server.addTool({
      name: "optionsData_realtimeOptions",
      description: "Fetches realtime options chain data. Premium endpoint.",
      parameters: schemas.OptionsDataRealtimeOptionsParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "optionsData_realtimeOptions",
          args,
          context,
          (av, params) => av.optionsData.realtimeOptions(params)
        ),
    });
  • Specific handler logic within the execute function: calls the AVantage library's optionsData.realtimeOptions method with params.
      (av, params) => av.optionsData.realtimeOptions(params)
    ),
  • Zod schema defining input parameters for the tool: symbol (required), contract (optional), datatype (optional).
    export const OptionsDataRealtimeOptionsParamsSchema = z.object({
      symbol: z.string().describe('The underlying stock symbol (e.g., "AAPL").'),
      contract: z.string().optional().describe('Specific option contract ID to fetch details for.'),
      datatype: DatatypeSchema.default('json').optional(),
    }).describe('Parameters for fetching realtime options chain data (Premium).')
  • Generic helper function used by all tools, including this one: manages Alpha Vantage API key and client instance via resource manager, invokes the specific AVantage method, handles errors, and returns JSON-stringified 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,' hinting at potential cost or access restrictions, but fails to describe critical behaviors like rate limits, authentication requirements, data freshness, or response format details. This leaves significant gaps for a tool fetching realtime 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—just two short sentences that directly state the tool's function and key characteristic. Every word earns its place with no redundancy or unnecessary elaboration, making it easy to parse quickly.

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 realtime options data and lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like rate limits or authentication, doesn't explain the output structure, and offers minimal context about when to use it. For a premium financial data tool, this leaves too many unknowns.

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 fully documents all parameters. The description adds no additional parameter semantics beyond what's in the schema, such as explaining the relationship between 'symbol' and 'contract' or clarifying data format implications. This meets the baseline for high schema coverage.

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 ('realtime options chain data'), making the purpose immediately understandable. It distinguishes this as a 'premium endpoint,' which differentiates it from potential free alternatives, though it doesn't explicitly contrast with sibling tools like 'optionsData_historicalOptions'.

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. It mentions it's a 'premium endpoint,' which implies cost or access restrictions, but doesn't specify when to choose realtime over historical options data or how it differs from other options-related tools.

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