Skip to main content
Glama
MCP-100

Stock Market MCP Server

by MCP-100

get_ticker_price

Retrieve current stock price data for any ticker symbol to monitor market values in real time.

Instructions

Get current price for a stock ticker

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock ticker symbol

Implementation Reference

  • Implements the core logic to fetch the latest intraday stock price for the given ticker symbol using the Alpha Vantage TIME_SERIES_INTRADAY API endpoint and formats the response as JSON.
    private async handleGetTickerPrice(args: any) {
      const response = await this.axiosInstance.get('', {
        params: {
          function: 'TIME_SERIES_INTRADAY',
          symbol: args.symbol,
          interval: '1min',
          outputsize: 'compact'
        }
      });
    
      const latestData = response.data['Time Series (1min)'];
      const latestTimestamp = Object.keys(latestData)[0];
      const price = latestData[latestTimestamp]['1. open'];
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            symbol: args.symbol,
            price: price,
            timestamp: latestTimestamp
          }, null, 2)
        }]
      };
    }
  • Input schema definition for the get_ticker_price tool, specifying an object with a required 'symbol' string property.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: {
          type: 'string',
          description: 'Stock ticker symbol'
        }
      },
      required: ['symbol']
    }
  • src/index.ts:53-66 (registration)
    Tool registration in the ListTools response, including name, description, and schema.
    {
      name: 'get_ticker_price',
      description: 'Get current price for a stock ticker',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: {
            type: 'string',
            description: 'Stock ticker symbol'
          }
        },
        required: ['symbol']
      }
    },
  • src/index.ts:114-115 (registration)
    Switch case in CallToolRequest handler that routes get_ticker_price calls to the handler function.
    case 'get_ticker_price':
      return await this.handleGetTickerPrice(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 states the tool gets current price, implying a read-only operation, but doesn't disclose any behavioral traits such as data source, refresh rates, error handling, or authentication needs. For a financial data tool with zero annotation coverage, this is a significant gap in transparency.

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, clear sentence with no wasted words. It's front-loaded with the core purpose ('Get current price for a stock ticker'), making it efficient and easy to parse. Every part of the sentence contributes directly to understanding the tool's function.

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?

Given the tool's low complexity (single parameter, no output schema, no annotations), the description is minimally complete. It covers the basic purpose but lacks details on behavioral aspects like data freshness or error cases. Without annotations or output schema, the description should ideally provide more context, but it's adequate for a simple lookup tool.

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 single parameter 'symbol' documented as 'Stock ticker symbol'. The description doesn't add any meaning beyond this, such as examples (e.g., 'AAPL' for Apple) or constraints (e.g., format requirements). With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 ('Get') and resource ('current price for a stock ticker'). It distinguishes the tool from siblings like 'get_company_overview' or 'get_financial_statement' by focusing on price data rather than broader company information. However, it doesn't explicitly mention that it's for real-time or current data versus historical, which could slightly limit differentiation.

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 scenarios where price data is needed over other financial information, nor does it reference sibling tools like 'get_market_report' for broader market context. This leaves the agent without explicit usage context.

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/MCP-100/stock-market-server'

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