stock-mcp

Query Stock Quote

query_stock_quote

查询个股实时行情，支持股票代码（如 sh600519、600519）或名称（如贵州茅台）。返回现价、涨跌额、涨跌幅、今开、昨收、最高、最低、成交量等数据。

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": {
      "stock": "<stock>"
    },
    "name": "query_stock_quote"
  }
}

Input Schema

Name	Required	Description	Default
`stock`	Yes	股票代码或名称，如 "sh600519"、"600519"、"贵州茅台"

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 9, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / stock / description

Added value: +"股票代码或名称，如 \"sh600519\"、\"600519\"、\"贵州茅台\""

removedInput schema / properties / stock / title
```
Removed value: -"Stock"
```

removedInput schema / title

Removed value: -"query_stock_quoteArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose that the data is real-time and enumerates the returned fields, but it says nothing about data source, latency/delay, which markets are covered, or what happens for an unknown code, all of which matter for a quote tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the purpose followed by input formats and return fields. The return-field list partially duplicates the output schema and is the one slightly wasteful element.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with a fully described schema and an output schema, the definition covers purpose, accepted inputs, and returned data. The remaining gap is market scope/freshness semantics, which is modest rather than disqualifying.

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% and the single parameter's schema already lists the same format examples (sh600519, 600519, 贵州茅台) that appear in the description. The description adds no parsing detail such as case sensitivity or prefix requirements, so the baseline 3 applies.

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 uses a specific verb+resource combination ('查询个股实时行情') and scopes it to individual stocks, which implicitly separates it from the index-oriented sibling. It does not name query_index explicitly, so an agent still has to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied (single-stock quotes) and the accepted input formats are spelled out with concrete examples, but there is no statement of when to prefer this over query_index or what to do for indices/other instruments. Nothing is misleading, but nothing routes the agent either.

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

All stock-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.