Skip to main content
Glama
kinmeic

Stock MCP Server

by kinmeic

stock_get

Retrieve real-time stock price data for individual stocks across multiple markets including A-shares, Hong Kong, and US stocks using stock codes and market identifiers.

Instructions

获取单只股票实时行情数据

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes股票代码,如 000858
marketYes市场: sh=上海, sz=深圳, hk=港股, us=美股

Implementation Reference

  • The MCP tool handler for 'stock_get' that processes tool requests, validates input using GetStockSchema, calls fetchStock, and returns formatted JSON response
    if (name === 'stock_get') {
      const params = GetStockSchema.parse(args);
      const data = await fetchStock(params.code, params.market as Market);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:102-119 (registration)
    Tool registration in the ListToolsRequestSchema handler that defines the 'stock_get' tool metadata and input schema including code and market parameters
      name: 'stock_get',
      description: '获取单只股票实时行情数据',
      inputSchema: {
        type: 'object',
        properties: {
          code: {
            type: 'string',
            description: '股票代码,如 000858',
          },
          market: {
            type: 'string',
            enum: ['sh', 'sz', 'hk', 'us'],
            description: '市场: sh=上海, sz=深圳, hk=港股, us=美股',
          },
        },
        required: ['code', 'market'],
      },
    },
  • Zod validation schema for stock_get input parameters that validates code (string) and market (enum: 'sh'|'sz'|'hk'|'us')
    const GetStockSchema = z.object({
      code: z.string().describe('股票代码,如 000858'),
      market: z.enum(['sh', 'sz', 'hk', 'us']).describe('市场: sh=上海, sz=深圳, hk=港股, us=美股'),
    });
  • Core implementation of fetchStock that constructs API URL based on market prefix, fetches data from Tencent's stock API, and parses the response into structured StockData
    export async function fetchStock(code: string, market: Market): Promise<StockData> {
      const prefix = getPrefix(market);
      const url = `${BASE_URL}/?q=${prefix}${code}`;
    
      const response = await fetch(url);
      if (!response.ok) {
        throw new Error(`Failed to fetch stock data: ${response.statusText}`);
      }
    
      const text = await response.text();
      const rawData = parseRawResponse(text);
    
      if (!rawData) {
        throw new Error(`No data returned for ${prefix}${code}`);
      }
    
      return parseStockData(rawData, market);
    }
  • Type definitions for stock_get including Market type, StockData union type (AStockData, HKStockData, USStockData), and their respective interfaces defining the structure of returned stock data
    // 股票市场类型
    export type Market = 'sh' | 'sz' | 'hk' | 'us';
    
    // 股票代码前缀
    export type StockPrefix = 'sh' | 'sz' | 'r_hk' | 's_us';
    
    // A股解析后的数据
    export interface AStockData {
      market: 'sh' | 'sz';
      name: string;
      code: string;
      currentPrice: number;
      yesterdayClose: number;
      open: number;
      volume: number;
      outside: number;
      inside: number;
      datetime: string;
      change: number;
      changePercent: number;
      high: number;
      low: number;
      amount: number;
      turnoverRate: number;    // 38 换手率
      peTtm: number;           // 39 市盈率TTM
      amplitude: number;      // 43 振幅
      totalMarketCap: number; // 44 总市值(亿)
      floatMarketCap: number;  // 45 流通市值(亿)
      volumeRatio: number;     // 49 量比
      avgPrice: number;        // 51 均价
      peDynamic: number;       // 52 市盈率(动)
      peStatic: number;        // 53 市盈率(静)
      floatingShares: number;  // 72 流通股
      totalShares: number;     // 73 总股本
      currency: string;       // 82 货币
      bidAsk?: {
        asks: Array<{ price: number; volume: number }>;
        bids: Array<{ price: number; volume: number }>;
      };
    }
    
    // 港股解析后的数据
    export interface HKStockData {
      market: 'hk';
      name: string;
      code: string;
      currentPrice: number;
      yesterdayClose: number;
      open: number;
      volume: number;
      datetime: string;
      change: number;
      changePercent: number;
      high: number;
      low: number;
      amount: number;
      pe: number;
      floatingShares: number;
      totalShares: number;
      currency: string;
    }
    
    // 美股解析后的数据
    export interface USStockData {
      market: 'us';
      name: string;
      code: string;
      currentPrice: number;
      change: number;
      changePercent: number;
      volume: number;
      amount: number;
      marketCap?: number;
      currency: string;
    }
    
    // 统一返回类型
    export type StockData = AStockData | HKStockData | USStockData;
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool gets real-time data but doesn't mention critical aspects like rate limits, data freshness, authentication requirements, error handling, or whether it's a read-only operation. This leaves significant gaps in understanding its operational behavior.

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 in Chinese that directly states the tool's purpose without any unnecessary words. It's front-loaded and appropriately sized for a simple data retrieval tool, 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 tool's complexity (simple retrieval with 2 parameters) and the lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral traits like rate limits or data format, and with no output schema, it fails to describe return values, leaving the agent uncertain about what to expect.

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 descriptions for both parameters ('code' and 'market'), including an enum for 'market'. The description doesn't add any extra semantic details beyond what the schema provides, such as examples or constraints, so it 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 verb ('获取' meaning 'get') and resource ('单只股票实时行情数据' meaning 'single stock real-time quote data'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from its sibling 'stock_get_batch', which handles multiple stocks, leaving room for confusion about when to use each.

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 like 'stock_get_batch' for multiple stocks or other sibling tools for positions and watches. It lacks context about prerequisites, such as needing valid stock codes and market identifiers, or any exclusions.

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/kinmeic/stock-mcp'

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