Skip to main content
Glama
deepsuthar496

Alpha Vantage MCP Server

get_stock_price

Retrieve real-time stock price data by entering a stock symbol to access current market values for investment analysis and tracking.

Instructions

Get real-time stock price information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesThe stock symbol (e.g., AAPL)

Implementation Reference

  • The handler function that executes the get_stock_price tool by querying the Alpha Vantage API's GLOBAL_QUOTE endpoint and returning the JSON response as text content.
    private async getStockPrice(args: any) {
      const response = await this.axiosInstance.get('', {
        params: {
          function: 'GLOBAL_QUOTE',
          symbol: args.symbol,
        },
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the get_stock_price tool, specifying an object with a required 'symbol' string property.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: {
          type: 'string',
          description: 'The stock symbol (e.g., AAPL)',
        },
      },
      required: ['symbol'],
    },
  • src/index.ts:93-106 (registration)
    Registration of the get_stock_price tool in the ListTools response, including name, description, and input schema.
    {
      name: 'get_stock_price',
      description: 'Get real-time stock price information',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: {
            type: 'string',
            description: 'The stock symbol (e.g., AAPL)',
          },
        },
        required: ['symbol'],
      },
    },
  • src/index.ts:53-54 (registration)
    Dispatch case in the CallToolRequestHandler switch statement that routes to the getStockPrice handler.
    case 'get_stock_price':
      return await this.getStockPrice(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. It mentions 'real-time' stock price information, which adds some context about data freshness, but fails to address critical aspects such as rate limits, authentication needs, error handling, or data source reliability. This leaves significant gaps for a tool that likely involves external API calls.

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.

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 lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral traits like rate limits or error responses, and with siblings offering related financial data, more context on differentiation is needed. For a tool that fetches real-time data, this minimal description leaves too many operational questions unanswered.

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, with the 'symbol' parameter clearly documented. The description doesn't add any semantic details beyond what the schema provides (e.g., it doesn't explain formatting constraints or provide examples beyond the schema's 'e.g., AAPL'). Baseline 3 is appropriate since the schema does the heavy lifting.

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 ('Get') and resource ('real-time stock price information'), making the purpose understandable. However, it doesn't explicitly differentiate from siblings like get_daily_time_series or get_company_overview, which could also provide stock-related data, so it falls short of 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. With siblings like get_daily_time_series (for historical data) and get_crypto_price (for cryptocurrencies), the agent lacks explicit direction on selecting this tool for real-time stock prices over other options.

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