Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

technicalIndicators_aroonosc

Calculate the Aroon Oscillator to identify trend strength and potential reversals for financial assets using symbol, interval, and time period inputs.

Instructions

Aroon Oscillator

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesThe stock symbol (e.g., "IBM").
intervalYesTime interval (e.g., "daily", "60min", "weekly"). Check Alpha Vantage docs for valid intervals per indicator.
datatypeNoData format for the response.json
monthNoSpecific month for intraday intervals (YYYY-MM format).
time_periodYesNumber of data points used to calculate the indicator.

Implementation Reference

  • src/index.ts:1325-1339 (registration)
    Registers the 'technicalIndicators_aroonosc' MCP tool, including its name, description, input schema, and handler that delegates to the generic executeAvantageTool with the specific AVantage library method.
    server.addTool({
      name: "technicalIndicators_aroonosc",
      description: "Aroon Oscillator",
      parameters: schemas.TechnicalIndicatorsAroonOscParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "technicalIndicators_aroonosc",
          args,
          context,
          (av, params) => av.technicalIndicators.aroonosc(params)
        ),
    });
  • Generic handler function that executes all AVantage-based tools. Manages API key resolution, AVantage instance via resourceManager, calls the library method (e.g., av.technicalIndicators.aroonosc), 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}`
        );
      }
    }
  • Exports the Zod input validation schema for the tool, which is an alias to TechnicalIndicatorsTimePeriodOnlyParamsSchema (includes symbol, interval, time_period, optional datatype/month).
    export const TechnicalIndicatorsAroonOscParamsSchema = TechnicalIndicatorsTimePeriodOnlyParamsSchema.describe('Parameters for AROONOSC.');
  • Base schema extended by the tool's params schema, adding time_period to common fields (symbol, interval, datatype, month).
    export const TechnicalIndicatorsTimePeriodOnlyParamsSchema = TechnicalIndicatorsCommonIndicatorParamsSchema.extend({
        time_period: z.string().describe('Number of data points used to calculate the indicator.'),
    }).describe('Parameters for indicators requiring symbol, interval, and time_period.');
  • Uses resourceManager to cache and reuse AVantage API client instances keyed by API key, ensuring efficient connection management.
    // 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)`);
      }
    );
Behavior1/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. 'Aroon Oscillator' reveals nothing about whether this is a read or write operation, what data source it accesses, what permissions might be required, rate limits, or what the output looks like. For a financial data tool with no annotation coverage, this is completely inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

While technically concise with just two words, this represents under-specification rather than effective brevity. The description fails to provide any useful information that would help an AI agent understand or use the tool. Every sentence should earn its place, but here there's essentially no meaningful content to evaluate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/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 5 parameters, no annotations, and no output schema, the description is completely inadequate. It provides no context about what the Aroon Oscillator measures, how it's calculated, what the output represents, or why someone would use this specific technical indicator. The description fails to compensate for the lack of structured metadata.

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 all parameters are documented in the input schema. The description adds no additional information about parameter meaning, constraints, or relationships. The baseline score of 3 reflects that the schema does the heavy lifting, but the description provides zero value beyond what's already in structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Aroon Oscillator' is essentially a tautology of the tool name 'technicalIndicators_aroonosc' and provides no meaningful information about what the tool actually does. It doesn't specify any action verb or resource, nor does it distinguish this technical indicator from the many other technical indicator tools in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance about when to use this tool versus alternatives. With 60+ sibling tools including many other technical indicators (AROON, ADOSC, BBANDS, etc.), there is no indication of what makes the Aroon Oscillator unique or when it should be selected over other technical analysis 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