Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

crypto_exchangeRates

Get real-time cryptocurrency exchange rates for trading pairs like BTC to USD. Convert between crypto and fiat currencies using current market data.

Instructions

Fetches the realtime exchange rate for a cryptocurrency pair (e.g., BTC to USD).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_currencyYesThe cryptocurrency symbol (e.g., "BTC").
to_currencyYesThe physical currency symbol (e.g., "USD").

Implementation Reference

  • src/index.ts:484-496 (registration)
    Registers the "crypto_exchangeRates" tool with MCP server, specifying name, description, input schema, and handler that calls the generic executeAvantageTool which invokes the Avantage library's crypto.exchangeRates method.
    server.addTool({
      name: "crypto_exchangeRates",
      description:
        "Fetches the realtime exchange rate for a cryptocurrency pair (e.g., BTC to USD).",
      parameters: schemas.CryptoExchangeRateParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool("crypto_exchangeRates", args, context, (av, params) =>
          av.crypto.exchangeRates(params.from_currency, params.to_currency)
        ),
    });
  • Defines the Zod input validation schema for the crypto_exchangeRates tool, requiring from_currency and to_currency parameters.
    export const CryptoExchangeRateParamsSchema = z.object({
        from_currency: z.string().describe('The cryptocurrency symbol (e.g., "BTC").'),
        to_currency: z.string().describe('The physical currency symbol (e.g., "USD").'),
    }).describe('Parameters for fetching cryptocurrency exchange rates.')
  • Shared helper function that manages AVantage client instances, executes the library method passed as avantageMethod (here, av.crypto.exchangeRates), handles authentication, errors, and returns JSON stringified data.
    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. While 'fetches' implies a read-only operation, it doesn't specify whether this requires authentication, has rate limits, what happens with invalid inputs, or the format of the returned data. The mention of 'realtime' is helpful but vague without context on latency or update frequency.

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 front-loads the core functionality. Every word contributes meaning, with no wasted text or redundancy. The example in parentheses is appropriately brief and illustrative.

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?

For a tool with no annotations and no output schema, the description is incomplete. It doesn't address key contextual aspects like authentication requirements, error handling, rate limits, or the structure of the returned exchange rate data. Given the complexity of financial data tools and the lack of structured metadata, more behavioral and operational context is needed.

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 schema description coverage is 100%, with clear parameter descriptions in the input schema. The description adds minimal value beyond the schema by providing an example ('e.g., BTC to USD'), but doesn't explain parameter semantics like valid currency symbols, case sensitivity, or format requirements. This meets the baseline 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 tool's purpose with a specific verb ('fetches') and resource ('realtime exchange rate for a cryptocurrency pair'), and provides an example ('e.g., BTC to USD'). However, it doesn't explicitly differentiate from sibling tools like 'crypto_daily' or 'crypto_intraday', which might also provide exchange rate data but with different timeframes or formats.

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 (e.g., 'crypto_daily', 'crypto_intraday', 'forex_exchangeRates'), there's no indication of whether this is the preferred tool for realtime rates, what distinguishes it from other crypto tools, or any prerequisites for use.

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