Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

technicalIndicators_atr

Calculate Average True Range (ATR) to measure market volatility for stocks using specified time intervals and periods, helping traders assess risk and set stop-loss levels.

Instructions

Average True Range (ATR)

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

  • The handler implementation for the 'technicalIndicators_atr' tool. It uses a generic executor that calls the Alpha Vantage library's technicalIndicators.atr method with validated parameters.
    server.addTool({
      name: "technicalIndicators_atr",
      description: "Average True Range (ATR)",
      parameters: schemas.TechnicalIndicatorsAtrParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "technicalIndicators_atr",
          args,
          context,
          (av, params) => av.technicalIndicators.atr(params)
        ),
    });
  • Zod schema for input parameters of the technicalIndicators_atr tool, extending the common time period schema with symbol, interval, time_period, and optional datatype/month.
    export const TechnicalIndicatorsAtrParamsSchema = TechnicalIndicatorsTimePeriodOnlyParamsSchema.describe('Parameters for ATR.');
  • src/index.ts:1532-1546 (registration)
    Registration of the 'technicalIndicators_atr' MCP tool on the FastMCP server instance.
    server.addTool({
      name: "technicalIndicators_atr",
      description: "Average True Range (ATR)",
      parameters: schemas.TechnicalIndicatorsAtrParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "technicalIndicators_atr",
          args,
          context,
          (av, params) => av.technicalIndicators.atr(params)
        ),
    });
  • Shared helper function that implements the core logic for all technical indicator tools, including API authentication, resource management, library invocation, and response formatting.
    /**
     * A generic function to execute an Avantage library method within an MCP tool.
     * Handles API key resolution, AVantage instance management via ResourceManager,
     * calling the library method, and handling the response/errors.
     *
     * @param toolName The name of the MCP tool (for logging).
     * @param args Validated tool arguments.
     * @param context MCP execution context containing extraArgs and requestId.
     * @param avantageMethod A function that takes the AVantage instance and args, and calls the appropriate library method.
     * @returns The stringified data from the Avantage library call.
     * @throws {UserError} If authentication fails or the library call returns an error.
     */
    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}`
        );
      }
    }
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. 'Average True Range (ATR)' gives no information about the tool's behavior—it doesn't mention whether it's a read-only operation, what data source it uses (e.g., Alpha Vantage), potential rate limits, error conditions, or the format of returned data. This is inadequate for a tool with parameters and no output schema.

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 concise with a single phrase, the description is under-specified rather than efficiently structured. It fails to front-load critical information like the tool's action or purpose, making it unhelpful for quick understanding. Conciseness should not come at the cost of clarity, and here it results in a lack of substantive content.

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 tool's complexity (5 parameters, no annotations, no output schema), the description is severely incomplete. It doesn't explain what the tool does, how to use it, what it returns, or any behavioral aspects. With no output schema to describe return values, the description should compensate but fails to do so, leaving the agent with insufficient information for effective tool invocation.

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 (e.g., symbol, interval, time_period). The description adds no additional meaning about parameters beyond what's in the schema, such as explaining how ATR calculation uses these inputs. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema carries the burden.

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 'Average True Range (ATR)' is essentially a tautology that restates the tool name with minimal expansion. It doesn't specify what action the tool performs (e.g., 'retrieves', 'calculates', or 'returns' ATR values) or what resource it operates on. While it identifies the technical indicator, it lacks a clear verb+resource combination that would make the purpose specific and actionable.

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 no guidance on when to use this tool versus alternatives. With many sibling tools in the technicalIndicators category (e.g., sma, ema, bbands), there's no indication of ATR's specific use case, such as volatility measurement, or when it might be preferred over other indicators. This leaves the agent without context for tool selection.

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