Skip to main content
Glama
Sign In
FactorHub MCP Server

FactorHub MCP Server

by michaelfeng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_trade_dates

Retrieve a list of trading days for the China A-share market within a specified date range. Input start and end dates to get the trading calendar.

Instructions

获取交易日历，查询指定时间段内的交易日列表。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trade_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_dateNo
end_dateNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

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

With no annotations provided, the description must fully convey behavior. It indicates a read-only query operation returning a list of trading days, which is sufficient for a simple retrieval tool. However, it does not disclose any constraints (e.g., date format, holiday treatment) or side effects.

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?

Single sentence, concise and front-loaded. No redundant words. However, it omits details that could be added without much bloat, like date format.

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?

Given there is an output schema (context signal), the description does not need to explain return values. The tool has two simple parameters with no required fields. The description is minimally adequate for a straightforward query tool, but lacks details on parameter constraints.

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?

Schema coverage is 0%, so description must compensate. It mentions '指定时间段' (specified time period) linking to start_date and end_date, but provides no format, default behavior, or meaning beyond what the parameter names imply. Minimal added value.

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 a list of trading days within a date range ('获取交易日历，查询指定时间段内的交易日列表'). It specifies both the verb (query) and the resource (trade dates), and it is distinguishable from sibling tools that deal with factors, indices, or stock info.

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 versus alternatives, no prerequisites or exclusions mentioned. The description only states the function without contextual usage direction.

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