Skip to main content
Glama
deepsuthar496

Alpha Vantage MCP Server

get_crypto_price

Retrieve current cryptocurrency prices in specified markets to monitor digital asset values and support financial analysis.

Instructions

Get cryptocurrency prices

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesThe crypto symbol (e.g., BTC)
marketYesMarket currency (e.g., USD)

Implementation Reference

  • The main handler function that executes the 'get_crypto_price' tool by querying the Alpha Vantage API with the CRYPTO_INTRADAY function and returning the JSON response.
    private async getCryptoPrice(args: any) {
      const response = await this.axiosInstance.get('', {
        params: {
          function: 'CRYPTO_INTRADAY',
          symbol: args.symbol,
          market: args.market,
        },
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:173-190 (registration)
    Registers the 'get_crypto_price' tool in the ListTools response, including its name, description, and input schema.
    {
      name: 'get_crypto_price',
      description: 'Get cryptocurrency prices',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: {
            type: 'string',
            description: 'The crypto symbol (e.g., BTC)',
          },
          market: {
            type: 'string',
            description: 'Market currency (e.g., USD)',
          },
        },
        required: ['symbol', 'market'],
      },
    },
  • Defines the input schema for the 'get_crypto_price' tool, specifying required 'symbol' and 'market' string parameters.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: {
          type: 'string',
          description: 'The crypto symbol (e.g., BTC)',
        },
        market: {
          type: 'string',
          description: 'Market currency (e.g., USD)',
        },
      },
      required: ['symbol', 'market'],
    },
  • Switch case in the CallTool request handler that dispatches 'get_crypto_price' calls to the getCryptoPrice method.
    case 'get_crypto_price':
      return await this.getCryptoPrice(request.params.arguments);
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. 'Get cryptocurrency prices' implies a read-only operation but doesn't specify rate limits, data sources, error handling, or output format. For a tool with no annotations, this is inadequate as it lacks critical behavioral details.

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 with zero waste. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration. Every word earns its place, making it highly concise.

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 a price-fetching tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the return values are (e.g., price, timestamp, volume), potential errors, or data freshness. This leaves significant gaps for an agent to understand the tool fully.

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 input schema has 100% description coverage, clearly documenting both parameters (symbol and market). The description adds no additional meaning beyond what the schema provides, such as examples or constraints. With high schema coverage, the baseline is 3, as the description doesn't compensate but also doesn't detract.

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 'Get cryptocurrency prices' clearly states the verb ('Get') and resource ('cryptocurrency prices'), making the purpose immediately understandable. It distinguishes this from sibling tools like get_stock_price and get_forex_rate by specifying cryptocurrency. However, it doesn't specify whether this retrieves current prices, historical data, or other details, which prevents a perfect score.

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. It doesn't mention sibling tools like get_stock_price or get_forex_rate, nor does it specify contexts or exclusions (e.g., for real-time vs. historical data). This leaves the agent with minimal usage direction.

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/deepsuthar496/alpha-ventage-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server