Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

forex_intraday

Fetch intraday time series data for Forex currency pairs to analyze short-term price movements and market trends using specified intervals.

Instructions

Fetches intraday time series data for a Forex pair.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_symbolYesThe currency symbol to convert from (e.g., "EUR").
to_symbolYesThe currency symbol to convert to (e.g., "USD").
intervalYesIntraday interval.
outputsizeNoOutput size. Compact returns latest 100 data points, Full returns complete history.compact
datatypeNoData format for the response.json

Implementation Reference

  • src/index.ts:723-734 (registration)
    Registers the 'forex_intraday' MCP tool with the server, defining its name, description, input schema, and execution handler that delegates to executeAvantageTool calling av.forex.intraday.
    server.addTool({
      name: "forex_intraday",
      description: "Fetches intraday time series data for a Forex pair.",
      parameters: schemas.ForexIntradayParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool("forex_intraday", args, context, (av, params) =>
          av.forex.intraday(params)
        ),
    });
  • Zod schema defining input parameters for the forex_intraday tool: from_symbol, to_symbol, interval, outputsize, datatype.
    export const ForexIntradayParamsSchema = z.object({
      from_symbol: z.string().describe('The currency symbol to convert from (e.g., "EUR").'),
      to_symbol: z.string().describe('The currency symbol to convert to (e.g., "USD").'),
      interval: MinuteIntervalsSchema,
      outputsize: OutputSizeSchema.default('compact').optional(),
      datatype: DatatypeSchema.default('json').optional(),
    }).describe('Parameters for fetching intraday Forex time series data.')
  • The execute handler function for the tool, which invokes the shared executeAvantageTool helper with the specific Alpha Vantage forex.intraday method.
    execute: (
      args,
      context // Let type be inferred
    ) =>
      executeAvantageTool("forex_intraday", args, context, (av, params) =>
        av.forex.intraday(params)
      ),
  • Shared helper function that manages Alpha Vantage API key, client instance via resource manager, executes the provided method, handles errors, and returns JSON stringified data. Used by all tools including forex_intraday.
    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}`
        );
      }
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Fetches' implies a read-only operation, it doesn't mention any rate limits, authentication requirements, data freshness, or potential costs/limitations. For a data-fetching tool with zero annotation coverage, this leaves significant behavioral gaps unaddressed.

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 sentence that immediately communicates the core function. There's no wasted language or unnecessary elaboration - every word serves the purpose of explaining what the tool does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (5 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks context about when to use it, behavioral constraints, or output format details. The 100% schema coverage helps, but the description itself doesn't provide enough guidance for optimal tool selection 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?

The description mentions 'intraday time series data' which hints at the interval parameter, but adds no meaningful semantic context beyond what's already in the schema (which has 100% coverage). The schema already thoroughly documents all 5 parameters with descriptions, enums, defaults, and requirements, so the description provides minimal additional value.

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

Purpose4/5

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

The description clearly states the action ('Fetches') and resource ('intraday time series data for a Forex pair'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'forex_daily' or 'forex_weekly' which likely fetch different timeframes, leaving some ambiguity about when to choose this specific intraday tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 available (including other forex tools like forex_daily, forex_weekly, forex_monthly, and forex_exchangeRates), there's no indication of when intraday data is appropriate versus daily, weekly, or other forex data sources.

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