PandaStock

Overview Schema Source Related Servers Discussions Admin

ChOptionNews

Fetch options-related news by date (YYYYMMDD) to track A-share options market events and support informed trading decisions.

Instructions

获取期权资讯。Get options-related news. Args: date (str): YYYYMMDD.

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": {
      "date": "<date>"
    },
    "name": "ChOptionNews"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.5Sep 27, 2026

TDQS

C2.9/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 the full behavioral burden, and it discloses essentially nothing: no statement of read-only behavior, no data source, no coverage window, no rate limits, no note on what a given date returns (e.g., non-trading days). Only the minimal implication of a data retrieval call is conveyed.

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?

Very short and front-loaded: purpose first, then the argument format. The bilingual duplication is mildly redundant but costs little, and nothing else is wasted.

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 one-parameter news fetch with an output schema present, the definition is minimally viable: return values need not be explained, but key context such as coverage window and how the date is interpreted is missing. An agent can call it, but with some uncertainty about semantics.

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 0% and the single parameter has no description, but the description compensates by specifying the intended format 'YYYYMMDD'. It adds nothing about timezone, trading-day behavior, or whether the date is required, so this is adequate rather than rich.

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?

States a specific verb and resource ('Get options-related news'), so an agent can tell it fetches news scoped to options. It does not explicitly distinguish itself from the news siblings (ChCoreNews, ChDomesticNews, ChGlobalNews), so sibling differentiation is only implied by the 'options' qualifier.

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?

There is no when-to-use guidance, no prerequisite context, and no mention of alternatives among the many news-listing siblings. The agent is left to infer that this is the options-specific news endpoint from the name alone.

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