Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

technicalIndicators_minusDM

Calculate Minus Directional Movement (-DM) to identify downward price momentum for stocks, using symbol, interval, and time period parameters to support technical analysis decisions.

Instructions

Minus Directional Movement (-DM)

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:1427-1441 (registration)
    MCP tool registration for 'technicalIndicators_minusDM', including name, description, input schema reference, and execute handler that delegates to Alpha Vantage library via executeAvantageTool.
    server.addTool({
      name: "technicalIndicators_minusDM",
      description: "Minus Directional Movement (-DM)",
      parameters: schemas.TechnicalIndicatorsMinusDmParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "technicalIndicators_minusDM",
          args,
          context,
          (av, params) => av.technicalIndicators.minusDM(params)
        ),
    });
  • Schema definition for the tool's input parameters, referencing the base time-period schema with specific description.
    export const TechnicalIndicatorsMinusDmParamsSchema = TechnicalIndicatorsTimePeriodOnlyParamsSchema.describe('Parameters for MINUS_DM.');
  • Shared utility function that orchestrates the execution of Alpha Vantage tools: manages API key, creates/reuses AVantage client via resource manager, invokes the specific method (e.g., technicalIndicators.minusDM), and returns JSON stringified data or errors appropriately for MCP.
    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, and the description offers no behavioral information. It doesn't disclose whether this is a read-only operation, its computational complexity, rate limits, or what the output entails (e.g., time-series data). For a tool with no annotations, this is a significant gap.

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?

The description is overly concise to the point of under-specification. A single phrase without sentence structure fails to convey essential information, making it inefficient rather than appropriately brief.

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 a technical indicator tool with no annotations and no output schema, the description is incomplete. It doesn't explain the tool's purpose, usage, or output, leaving the agent with insufficient context to invoke 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%, so the schema fully documents all 5 parameters. The description adds no parameter semantics beyond what's in the schema, meeting the baseline score of 3 where the schema handles the heavy lifting.

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 'Minus Directional Movement (-DM)' restates the tool name with minimal elaboration, making it a tautology. It doesn't specify what the tool actually does (e.g., calculates a technical indicator for a given stock symbol) or distinguish it from sibling tools like 'technicalIndicators_plusDM' or 'technicalIndicators_minusDI'.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about its application in technical analysis, prerequisites, or comparisons to sibling tools (e.g., 'technicalIndicators_plusDM' for positive directional movement).

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