Real-time Stock MCP Service

get_smart_score

Retrieve the smart score for a Chinese stock by providing its stock code with exchange suffix. Returns a quantitative evaluation.

Instructions

获取股票智能评分数据

Args: stock_code: 股票代码，要在数字后加上交易所代码，格式如300750.SZ Examples: - get_smart_score("300750.SZ")

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_code": "<stock_code>"
    },
    "name": "get_smart_score"
  }
}

Input Schema

Name	Required	Description	Default
`stock_code`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1May 17, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states '获取' (get), implying a read operation, but lacks details on side effects, authentication needs, or whether it is read-only. The description adds minimal behavioral context beyond the name.

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 concise, with a clear purpose followed by structured Args and Examples. Every sentence is meaningful and earns its place.

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?

With an output schema present, the description need not explain return values. However, the lack of behavioral transparency and usage guidelines makes the description less complete for a tool with no annotations. The parameter explanation is thorough, but other aspects are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, but the description fully explains the parameter 'stock_code' with the format required (add exchange code like 300750.SZ) and provides an example. This greatly adds meaning beyond the bare schema.

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 it '获取股票智能评分数据' (gets stock smart score data), specifying the resource and action. The sibling tool 'get_smart_score_rank' suggests differentiation, but the description does not explicitly contrast with siblings.

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?

The description provides an example and explains the parameter format (adding exchange code), but does not specify when to use this tool versus alternatives like 'get_smart_score_rank' or other data retrieval tools.

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