Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

technicalIndicators_htDcperiod

Calculate the dominant cycle period using Hilbert Transform to identify market cycles for financial analysis and trading decisions.

Instructions

Hilbert Transform - Dominant Cycle Period

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).
series_typeYesThe desired price type.

Implementation Reference

  • src/index.ts:1179-1193 (registration)
    Registration of the MCP tool 'technicalIndicators_htDcperiod' with server.addTool, specifying name, description, parameters schema, and inline execute handler that delegates to executeAvantageTool.
    server.addTool({
      name: "technicalIndicators_htDcperiod",
      description: "Hilbert Transform - Dominant Cycle Period",
      parameters: schemas.TechnicalIndicatorsHtDcperiodParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "technicalIndicators_htDcperiod",
          args,
          context,
          (av, params) => av.technicalIndicators.htDcperiod(params)
        ),
    });
  • Zod schema for input parameters of the tool, extending common indicator params with series_type.
    export const TechnicalIndicatorsHtDcperiodParamsSchema = TechnicalIndicatorsCommonIndicatorParamsSchema.extend({ series_type: SeriesTypeSchema }).describe('Parameters for HT_DCPERIOD.');
  • Inline handler function for the tool execution, which calls the shared executeAvantageTool with the specific AVantage method for HT_DCPERIOD.
    execute: (
      args,
      context // Let type be inferred
    ) =>
      executeAvantageTool(
        "technicalIndicators_htDcperiod",
        args,
        context,
        (av, params) => av.technicalIndicators.htDcperiod(params)
      ),
  • Shared helper function used by all tools to manage AVantage client resources, perform API calls via the provided method, handle errors, and return 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}`
        );
      }
    }
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. However, it offers no information on what the tool does behaviorally—such as whether it performs calculations, retrieves data, requires authentication, has rate limits, or returns specific formats. The description is purely a label with no operational details, failing to compensate for the lack of annotations.

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 a single phrase that is overly concise to the point of under-specification. It lacks structure (e.g., no introductory sentence explaining the tool's function) and does not front-load key information, making it inefficient for quick comprehension. While brief, it fails to convey necessary details, so it scores low for not earning its place with useful content.

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 5 parameters, no annotations, and no output schema, the description is incomplete. It does not explain what the tool returns (e.g., numerical values, charts, or time-series data), how results should be interpreted, or any dependencies on external data sources. The description alone is insufficient for an agent to understand the tool's full context and usage.

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%, meaning all parameters are documented in the input schema. The description adds no additional meaning or context for parameters beyond what the schema provides (e.g., it does not explain how parameters like 'symbol' or 'interval' relate to the Hilbert Transform calculation). With high schema coverage, the baseline score is 3, as the description does not enhance parameter understanding but also does not detract from it.

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 'Hilbert Transform - Dominant Cycle Period' restates the tool name with minimal elaboration, making it a tautology. It lacks a clear verb or action (e.g., 'calculate' or 'retrieve'), and does not specify what resource or data it operates on (e.g., stock data). While it hints at a technical indicator, it fails to distinguish this from sibling tools like 'technicalIndicators_htDcphase' or 'technicalIndicators_htSine', which are also Hilbert Transform-based indicators.

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. It does not mention any context, prerequisites, or comparisons to sibling tools (e.g., other technical indicators like 'technicalIndicators_sma' or 'technicalIndicators_bbands'), leaving the agent with no information to make an informed selection among similar 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