Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

technicalIndicators_htSine

Analyze stock price cycles using Hilbert Transform Sine Wave to identify market turning points and trend reversals for technical trading decisions.

Instructions

Hilbert Transform - Sine Wave

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:1149-1163 (registration)
    Registers the 'technicalIndicators_htSine' tool with the MCP server, providing name, description, parameters schema, and inline execute handler that delegates to executeAvantageTool.
    server.addTool({
      name: "technicalIndicators_htSine",
      description: "Hilbert Transform - Sine Wave",
      parameters: schemas.TechnicalIndicatorsHtSineParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "technicalIndicators_htSine",
          args,
          context,
          (av, params) => av.technicalIndicators.htSine(params)
        ),
    });
  • The execute handler function for the tool, which calls the shared executeAvantageTool helper with the specific AVantage library method.
    execute: (
      args,
      context // Let type be inferred
    ) =>
      executeAvantageTool(
        "technicalIndicators_htSine",
        args,
        context,
        (av, params) => av.technicalIndicators.htSine(params)
      ),
  • Zod schema defining the input parameters for the technicalIndicators_htSine tool, extending common params with series_type.
    export const TechnicalIndicatorsHtSineParamsSchema = TechnicalIndicatorsCommonIndicatorParamsSchema.extend({ series_type: SeriesTypeSchema }).describe('Parameters for HT_SINE.');
  • Shared helper function that all tools use: manages Alpha Vantage client instance, performs the API call via the provided method, and handles responses/errors.
    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?

With no annotations provided, the description carries full burden but offers no behavioral details. It does not disclose whether this is a read-only operation, what data sources it uses (e.g., Alpha Vantage), potential rate limits, authentication needs, or output characteristics (e.g., returns sine and lead sine values). The agent is left guessing about critical operational traits.

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 'Hilbert Transform - Sine Wave', which is overly concise to the point of under-specification. It lacks structure (e.g., no verb or context) and fails to front-load key information, making it inefficient rather than succinct. Every word earns its place, but too few words are used to be helpful.

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., sine wave values for trend analysis), how it behaves, or when to use it, leaving significant gaps for an AI agent to infer functionality from the name and schema alone.

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 (symbol, interval, datatype, month, series_type) with descriptions and enums. The description adds no parameter semantics beyond the schema, not even hinting at how parameters relate to the Hilbert Transform calculation. Baseline 3 is appropriate as the schema does 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 'Hilbert Transform - Sine Wave' restates the tool name with minimal elaboration, providing only the technical indicator name without specifying what it does (e.g., calculates sine wave components for trend analysis) or what resource it operates on (e.g., stock data). It fails to distinguish from sibling tools like 'technicalIndicators_htPhasor' or 'technicalIndicators_htTrendline', leaving the purpose vague beyond the indicator category.

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, such as other Hilbert Transform indicators (e.g., htPhasor, htTrendline) or general technical indicators. The description lacks context about its application (e.g., for cyclical analysis), prerequisites, or exclusions, offering no help in tool selection among the many siblings.

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