Skip to main content
Glama
Sign In
FactorHub MCP Server

FactorHub MCP Server

by michaelfeng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_market_daily

Retrieve daily OHLCV and percentage change data for a Chinese stock by providing its ts_code, with optional date range filtering.

Instructions

获取个股日线行情数据（OHLCV + 涨跌幅）。ts_code 如 000001.SZ、600519.SH。

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": {
      "ts_code": "<ts_code>"
    },
    "name": "get_market_daily"
  }
}

Input Schema

NameRequiredDescriptionDefault
ts_codeYes
start_dateNo
end_dateNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description must carry the burden. It does not disclose whether the tool is read-only, any side effects, authentication needs, or rate limits. Only the data content (OHLCV + 涨跌幅) is mentioned.

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 extremely concise: two short sentences. The first states purpose and output, the second provides an example. No unnecessary text.

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?

Despite having an output schema, the description lacks explanation of return format, date handling, and usage context. For a tool with 3 parameters and no annotations, this is insufficient.

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

Parameters2/5

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

With 0% schema description coverage, the description should compensate but only provides a ts_code example. The format for start_date and end_date is not explained, and no default values or valid formats are given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: '获取个股日线行情数据' (get daily stock market data) with specific fields (OHLCV + 涨跌幅). It distinguishes from siblings like get_index_daily by focusing on individual stocks.

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?

No guidance on when to use this tool over alternatives (e.g., get_index_daily for indices) or prerequisites. The example only shows ts_code format, lacking context like date range conventions.

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