Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

forex_daily

Fetch daily time series data for Forex currency pairs to analyze exchange rate trends and historical performance.

Instructions

Fetches daily 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").
outputsizeNoOutput size. Compact returns latest 100 data points, Full returns complete history.compact
datatypeNoData format for the response.json

Implementation Reference

  • src/index.ts:736-747 (registration)
    Registration of the 'forex_daily' MCP tool, including name, description, input schema reference, and execute handler that calls the generic executeAvantageTool with the specific AVantage library method av.forex.daily(params).
    server.addTool({
      name: "forex_daily",
      description: "Fetches daily time series data for a Forex pair.",
      parameters: schemas.ForexDailyParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool("forex_daily", args, context, (av, params) =>
          av.forex.daily(params)
        ),
    });
  • Zod schema definition for the input parameters of the forex_daily tool: from_symbol, to_symbol, optional outputsize and datatype.
    export const ForexDailyParamsSchema = 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").'),
      outputsize: OutputSizeSchema.default('compact').optional(),
      datatype: DatatypeSchema.default('json').optional(),
    }).describe('Parameters for fetching daily Forex time series data.')
  • The execute handler function for forex_daily, invoking executeAvantageTool with tool-specific AVantage forex.daily method call.
    execute: (
      args,
      context // Let type be inferred
    ) =>
      executeAvantageTool("forex_daily", args, context, (av, params) =>
        av.forex.daily(params)
      ),
  • Generic helper function executeAvantageTool that implements the core logic for all AVantage-based tools: resolves API key, manages AVantage client instances, executes the provided library method, handles errors, and returns JSON data. Used by forex_daily handler.
    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 but offers minimal behavioral insight. It states 'Fetches' implying a read operation, but doesn't disclose critical traits like rate limits, authentication needs, data latency, or error handling. For a data-fetching tool with zero annotation coverage, this is a significant gap in transparency.

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 directly states the tool's function without unnecessary words. It's front-loaded with the core purpose, making it easy to parse quickly, and every part of the sentence contributes essential information.

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 (fetching financial time series data), lack of annotations, and no output schema, the description is insufficient. It doesn't explain the return format (e.g., time series structure), data granularity, or potential limitations, leaving the agent under-informed for proper invocation and result interpretation.

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 parameters (from_symbol, to_symbol, outputsize, datatype) with clear descriptions and enums. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline score of 3 for high schema coverage.

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 ('daily time series data for a Forex pair'), making the purpose immediately understandable. It distinguishes from siblings like forex_intraday or forex_weekly by specifying 'daily' frequency, though it doesn't explicitly contrast with forex_exchangeRates which might serve different data types.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention sibling tools (e.g., forex_intraday for higher frequency, forex_exchangeRates for spot rates) or contextual factors like data freshness or use cases, leaving the agent to infer usage from the name alone.

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