Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

forex_weekly

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

Instructions

Fetches weekly 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").
datatypeNoData format for the response.json

Implementation Reference

  • src/index.ts:749-760 (registration)
    Registers the 'forex_weekly' MCP tool with the FastMCP server, including name, description, input schema reference, and execute handler that delegates to Alpha Vantage library.
    server.addTool({
      name: "forex_weekly",
      description: "Fetches weekly time series data for a Forex pair.",
      parameters: schemas.ForexWeeklyMonthlyParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool("forex_weekly", args, context, (av, params) =>
          av.forex.weekly(params)
        ),
    });
  • Defines the Zod validation schema for the input parameters of the 'forex_weekly' tool, requiring from_symbol and to_symbol, with optional datatype.
    export const ForexWeeklyMonthlyParamsSchema = 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").'),
      datatype: DatatypeSchema.default('json').optional(),
    }).describe('Parameters for fetching weekly/monthly Forex time series data.')
  • The execute handler function for the 'forex_weekly' tool, which invokes the generic executeAvantageTool and provides the specific callback to call av.forex.weekly(params).
    execute: (
      args,
      context // Let type be inferred
    ) =>
      executeAvantageTool("forex_weekly", args, context, (av, params) =>
        av.forex.weekly(params)
      ),
  • Generic helper function used by all tools, including 'forex_weekly', to manage AVantage instance, perform API calls, handle authentication, caching, and 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}`
        );
      }
    }
Behavior2/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 mentions 'fetches' which implies a read operation, but doesn't specify whether this requires authentication, has rate limits, returns paginated data, or includes metadata like timestamps. For a data-fetching tool with zero annotation coverage, this leaves critical behavioral traits undocumented.

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 appropriately sized for a straightforward data-fetching tool and front-loads the core purpose effectively.

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?

For a simple data retrieval tool with 3 parameters and no output schema, the description is minimally adequate but incomplete. It covers the basic purpose but lacks behavioral context (no annotations) and doesn't explain what the returned data looks like (no output schema). The 100% schema coverage helps, but overall completeness is limited to the bare essentials.

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%, with clear descriptions for all parameters (from_symbol, to_symbol, datatype). The description adds no additional parameter semantics beyond what the schema provides, such as explaining Forex pair conventions or datatype implications. Baseline 3 is appropriate when the schema does all the documentation work.

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 verb ('fetches') and resource ('weekly time series data for a Forex pair'), making the purpose specific and understandable. However, it doesn't distinguish this tool from sibling tools like 'forex_daily' or 'forex_monthly' that likely fetch similar data at different frequencies, leaving some ambiguity about when to choose this specific 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 sibling tools like 'forex_daily', 'forex_monthly', and 'forex_intraday' available, the agent has no indication whether this tool is for historical analysis, real-time data, or specific use cases, leaving usage decisions to guesswork.

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