Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

technicalIndicators_htDcphase

Analyze stock price cycles using the Hilbert Transform Dominant Cycle Phase indicator to identify market timing signals for trading decisions.

Instructions

Hilbert Transform - Dominant Cycle Phase

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:1194-1208 (registration)
    Registers the MCP tool 'technicalIndicators_htDcphase' with name, description, input schema, and an inline execute handler that delegates to the generic executeAvantageTool with the specific AVantage library method.
    server.addTool({
      name: "technicalIndicators_htDcphase",
      description: "Hilbert Transform - Dominant Cycle Phase",
      parameters: schemas.TechnicalIndicatorsHtDcphaseParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "technicalIndicators_htDcphase",
          args,
          context,
          (av, params) => av.technicalIndicators.htDcphase(params)
        ),
    });
  • Zod schema definition for the tool's input parameters, extending the common technical indicator params with series_type.
    export const TechnicalIndicatorsHtDcphaseParamsSchema = TechnicalIndicatorsCommonIndicatorParamsSchema.extend({ series_type: SeriesTypeSchema }).describe('Parameters for HT_DCPHASE.');
  • Generic helper function used by all tools, including this one, to execute the AVantage library method. Manages authentication, caching of AVantage instances, calls the specific indicator method, and formats the response.
    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}`
        );
      }
    }
  • The specific execute handler for the tool, which passes the tool name, args, context, and the AVantage method av.technicalIndicators.htDcphase to the generic executor.
    execute: (
      args,
      context // Let type be inferred
    ) =>
      executeAvantageTool(
        "technicalIndicators_htDcphase",
        args,
        context,
        (av, params) => av.technicalIndicators.htDcphase(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. It offers no information about what the tool returns (e.g., phase values, timestamps), whether it's a read-only operation, potential rate limits, authentication needs, or data sources. The description is purely a label with no behavioral context.

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 (one phrase), the description is under-specified rather than efficiently structured. It fails to front-load essential information about the tool's purpose or behavior. The single phrase doesn't earn its place by adding value beyond the tool name.

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 (technical indicator with 5 parameters), no annotations, and no output schema, the description is completely inadequate. It doesn't explain what the tool does, when to use it, what it returns, or any behavioral traits. The description fails to compensate for the lack of structured information.

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 information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 Phase' restates the tool name/function without explaining what it does. It doesn't specify the action (e.g., 'calculate', 'retrieve', 'analyze') or the resource (e.g., 'stock data', 'technical indicator values'). While it hints at a technical indicator, the purpose remains vague and tautological.

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., htDcperiod, htPhasor, htSine), there's no indication of how this specific Hilbert Transform indicator differs or when it's appropriate. No context or exclusions are mentioned.

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