Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

technicalIndicators_adosc

Calculate the Chaikin A/D Oscillator to analyze stock momentum and volume flow using specified time intervals and period settings for trading decisions.

Instructions

Chaikin A/D 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).
fastperiodNoFast period setting (integer).
slowperiodNoSlow period setting (integer).

Implementation Reference

  • The handler function for the 'technicalIndicators_adosc' tool, registered via server.addTool. It invokes the shared executeAvantageTool helper, which calls the Alpha Vantage library's technicalIndicators.adosc method.
    server.addTool({
      name: "technicalIndicators_adosc",
      description: "Chaikin A/D Oscillator",
      parameters: schemas.TechnicalIndicatorsFastSlowIndicatorParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "technicalIndicators_adosc",
          args,
          context,
          (av, params) => av.technicalIndicators.adosc(params)
        ),
    });
  • Zod schema defining input parameters for fast/slow period technical indicators like ADOSC, extending the common params.
    export const TechnicalIndicatorsFastSlowIndicatorParamsSchema = TechnicalIndicatorsCommonIndicatorParamsSchema.extend({
      fastperiod: z.string().optional().describe('Fast period setting (integer).'),
      slowperiod: z.string().optional().describe('Slow period setting (integer).'),
    }).describe('Parameters for indicators with fast/slow period settings.')
  • Base Zod schema for common technical indicator parameters (symbol, interval, etc.), extended by the fast/slow schema.
    export const TechnicalIndicatorsCommonIndicatorParamsSchema = z.object({
      symbol: z.string().describe('The stock symbol (e.g., "IBM").'),
      interval: z.string().describe('Time interval (e.g., "daily", "60min", "weekly"). Check Alpha Vantage docs for valid intervals per indicator.'),
      datatype: DatatypeSchema.default('json').optional(),
      month: z.string().optional().describe('Specific month for intraday intervals (YYYY-MM format).'),
    }).describe('Common parameters for many technical indicators.')
  • Shared utility function that manages authentication, AVantage client lifecycle via ResourceManager, executes the library method, and formats the response for all Alpha Vantage-based MCP tools.
    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}`
        );
      }
    }
  • src/index.ts:1102-1116 (registration)
    Explicit registration of the 'technicalIndicators_adosc' tool on the MCP server with name, description, parameters schema, and execute handler.
    server.addTool({
      name: "technicalIndicators_adosc",
      description: "Chaikin A/D Oscillator",
      parameters: schemas.TechnicalIndicatorsFastSlowIndicatorParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "technicalIndicators_adosc",
          args,
          context,
          (av, params) => av.technicalIndicators.adosc(params)
        ),
    });
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. The description reveals nothing about what this tool actually does - whether it calculates values, retrieves historical data, requires authentication, has rate limits, or what format/scope of results to expect. For a technical indicator tool with no annotation coverage, this complete lack of behavioral information is 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 three words, this represents under-specification rather than effective conciseness. The description fails to provide the essential information an agent needs to understand and use the tool. Every sentence should earn its place, but here the single 'sentence' (really just a label) doesn't fulfill its purpose of explaining the tool's function.

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?

Given the complexity of a technical indicator tool with 6 parameters, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what the tool returns, how to interpret results, what the Chaikin A/D Oscillator measures, or any context about its financial analysis application. For a tool that presumably calculates a specific technical indicator, this minimal description leaves the agent with insufficient information to use it effectively.

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%, with all 6 parameters well-documented in the input schema. The description adds no parameter information beyond what's already in the structured schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description. The description doesn't compensate but doesn't need to given the comprehensive schema documentation.

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 'Chaikin A/D Oscillator' is a tautology that restates the tool name without explaining what it does. It doesn't specify the verb (e.g., 'calculate' or 'retrieve') or clarify that this is a technical indicator for financial analysis. While the name suggests it's related to technical indicators, the description adds no meaningful clarification beyond the name itself.

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 on when to use this tool versus alternatives. With 70+ sibling tools including many other technical indicators (like technicalIndicators_ad, technicalIndicators_aroon, technicalIndicators_bbands), there's no indication of what distinguishes the Chaikin A/D Oscillator from other momentum or volume-based indicators. No context about appropriate use cases is provided.

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