Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

technicalIndicators_mama

Calculate the MESA Adaptive Moving Average (MAMA) technical indicator for financial analysis. Use this tool to analyze stock price trends and generate adaptive moving averages based on specified parameters like symbol, interval, and price type.

Instructions

MESA Adaptive Moving Average (MAMA)

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).
fastlimitNoFast limit parameter for MAMA.0.01
slowlimitNoSlow limit parameter for MAMA.0.01
series_typeYesThe desired price type.

Implementation Reference

  • src/index.ts:1226-1240 (registration)
    Registers the 'technicalIndicators_mama' MCP tool with name, description, input schema, and an inline execute handler that uses the shared executeAvantageTool helper to invoke the Alpha Vantage MAMA technical indicator method.
    server.addTool({
      name: "technicalIndicators_mama",
      description: "MESA Adaptive Moving Average (MAMA)",
      parameters: schemas.TechnicalIndicatorsMamaIndicatorParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool(
          "technicalIndicators_mama",
          args,
          context,
          (av, params) => av.technicalIndicators.mama(params)
        ),
    });
  • Defines the Zod input schema for the tool, extending common technical indicator params with MAMA-specific fastlimit and slowlimit parameters, and series_type.
    // Schema for MAMA indicator
    export const TechnicalIndicatorsMamaIndicatorParamsSchema = TechnicalIndicatorsCommonIndicatorParamsSchema.extend({
      fastlimit: z.string().optional().default('0.01').describe('Fast limit parameter for MAMA.'),
      slowlimit: z.string().optional().default('0.01').describe('Slow limit parameter for MAMA.'),
      series_type: SeriesTypeSchema,
    }).describe('Parameters for the MAMA technical indicator.')
  • Shared helper function used by all tools (including technicalIndicators_mama) to manage Alpha Vantage client lifecycle, execute the specific library method, handle authentication/errors, and return JSON results.
    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 adds no behavioral context beyond the name. It doesn't disclose whether this is a read-only operation, its data source (e.g., Alpha Vantage), rate limits, authentication needs, or output format, which is critical 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient phrase with no wasted words, making it front-loaded and easy to parse. It's appropriately sized for its limited content, though this conciseness comes at the cost of detail.

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 tool's complexity (7 parameters, no output schema, and no annotations), the description is incomplete. It lacks context on what the tool returns, how results are structured, or any behavioral traits, making it inadequate for effective agent use despite the detailed input schema.

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 input schema fully documents all 7 parameters. The description adds no additional meaning about parameters, such as explaining 'MAMA' specifics or parameter interactions, but the schema provides adequate details, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'MESA Adaptive Moving Average (MAMA)' states what the tool does by naming the specific technical indicator, but it's vague about the action (e.g., 'calculate' or 'retrieve') and doesn't distinguish it from sibling tools like 'technicalIndicators_sma' or 'technicalIndicators_ema'. It provides the indicator name but lacks a clear verb-resource pairing.

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 offers no guidance on when to use this tool versus alternatives, such as other technical indicators in the sibling list. There's no mention of use cases, prerequisites, or comparisons, leaving the agent with no context for 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