Skip to main content
Glama
Sign In
Stock MCP Server

Stock MCP Server

by kinmeic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

stock_get_batch

Retrieve real-time market data for multiple stocks simultaneously to monitor portfolio performance across A-shares, Hong Kong, and US markets.

Instructions

批量获取多只股票实时行情数据

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "stocks": "<stocks>"
    },
    "name": "stock_get_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
stocksYes股票列表

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose rate limits, authentication needs, data freshness guarantees, error handling, or response format. '实时行情数据' implies real-time data but doesn't specify update frequency or latency.

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 Chinese phrase that directly conveys the core functionality without any wasted words. It's appropriately sized for a straightforward batch data retrieval tool.

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?

For a data retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what data is returned (e.g., price, volume, change), format, error conditions, or limitations (e.g., maximum batch size). The context signals show minimal parameter complexity but the behavioral aspects are undocumented.

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% with the parameter 'stocks' documented as '股票列表'. The description adds no additional parameter semantics beyond what's in the schema. The baseline is 3 since the schema adequately covers the single parameter.

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/fetch) and resource (多只股票实时行情数据 - multiple stocks' real-time market data). It distinguishes from sibling 'stock_get' by specifying batch operation, though it doesn't explicitly mention how it differs from other stock-related tools that might not exist.

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' (single stock) or other position/watch tools. It doesn't mention prerequisites, limitations, or typical use cases for batch versus individual queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools