Skip to main content
Glama
MissionSquad

MCP Avantage

by MissionSquad

crypto_intraday

Fetch intraday cryptocurrency price data for analysis and trading decisions. Specify symbol, market, and interval to retrieve time series data in JSON or CSV format.

Instructions

Fetches intraday time series data for a cryptocurrency.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesThe cryptocurrency symbol (e.g., "BTC").
marketYesThe exchange market (e.g., "USD", "EUR").
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:498-509 (registration)
    Registers the 'crypto_intraday' MCP tool with name, description, input schema, and execute handler using server.addTool.
    server.addTool({
      name: "crypto_intraday",
      description: "Fetches intraday time series data for a cryptocurrency.",
      parameters: schemas.CryptoIntradayParamsSchema,
      execute: (
        args,
        context // Let type be inferred
      ) =>
        executeAvantageTool("crypto_intraday", args, context, (av, params) =>
          av.crypto.intraday(params)
        ),
    });
  • Zod schema defining input parameters: symbol, market, interval, outputsize, datatype for the crypto_intraday tool.
    export const CryptoIntradayParamsSchema = z.object({
      symbol: z.string().describe('The cryptocurrency symbol (e.g., "BTC").'),
      market: z.string().describe('The exchange market (e.g., "USD", "EUR").'),
      interval: MinuteIntervalsSchema,
      outputsize: OutputSizeSchema.default('compact').optional(),
      datatype: DatatypeSchema.default('json').optional(),
    }).describe('Parameters for fetching intraday crypto time series data.')
  • The execute handler function for the tool, which invokes executeAvantageTool and ultimately calls av.crypto.intraday(params) on the AVantage client.
    execute: (
      args,
      context // Let type be inferred
    ) =>
      executeAvantageTool("crypto_intraday", args, context, (av, params) =>
        av.crypto.intraday(params)
      ),
  • Generic helper function that manages AVantage client instances, performs the API call via the provided method, handles errors, and returns the result as JSON string. Used by all tools including crypto_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?

No annotations are provided, so the description carries full burden. It states the action ('fetches') but doesn't disclose behavioral traits like rate limits, authentication requirements, data freshness, error handling, or response format details. For a data-fetching tool with no annotation coverage, this leaves significant gaps in understanding its operational characteristics.

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 and front-loaded with the core purpose, making it easy to parse quickly.

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 complexity of financial data tools and the absence of both annotations and output schema, the description is insufficient. It doesn't explain what the returned time series data looks like, how historical data is handled, or any limitations. For a tool with 5 parameters and no structured output documentation, more contextual information would be needed for effective use.

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 parameters are fully documented in the schema. The description doesn't add any meaningful parameter semantics beyond what's already in the schema descriptions (e.g., explaining what 'symbol' or 'interval' mean in practice). Baseline 3 is appropriate when the schema does all the parameter 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 ('intraday time series data for a cryptocurrency'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'crypto_daily' or 'forex_intraday', which would require mentioning the time granularity or asset class distinction.

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 for different timeframes (e.g., crypto_daily, crypto_weekly) and asset classes (e.g., forex_intraday), there's no indication of appropriate contexts, prerequisites, or exclusions for this intraday crypto data tool.

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