Real-time Stock MCP Service

get_business_scope

Retrieve the main business scope of a Chinese stock by providing its stock code with exchange suffix.

Instructions

获取主营业务范围

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

Returns: 主营业务范围文本

Examples: - get_business_scope("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_business_scope"
  }
}

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

B3.1/5.0

Behavior2/5

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

No annotations are provided, and the description only states it returns text. It lacks disclosure of latency, rate limits, or any side effects, which would be needed for a minimally transparent description.

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?

The description is brief and structured with Args, Returns, and Examples sections, conveying necessary information without extraneous content.

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?

For a simple retrieval tool with one parameter and minimal output, the description covers the essential usage. However, it omits details like data freshness or limits, which could be useful given the output schema is not shown.

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

Parameters4/5

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

Schema coverage is 0%, but the description adds meaningful context by specifying the stock code format with exchange code and an example, significantly aiding parameter understanding 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?

Description clearly states the tool retrieves the main business scope for a stock, with a specific verb and resource. It differentiates from siblings like get_business_review and get_main_business through the term 'scope'.

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?

Provides the required format for the stock code parameter, but no guidance on when to use this tool versus alternatives or when not to use it.

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