PandaStock

by D-Asce

Overview Schema Source Related Servers Discussions Admin

Python

Local

ChCoreNews

Fetch core market news for a specified date to review A-share highlights. Input YYYYMMDD to retrieve daily key updates.

Instructions

获取核心资讯。Get core market news. Args: date (str): YYYYMMDD like "20260818".

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": "ChCoreNews"
  }
}

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?

With no annotations, the description carries the full behavioral burden. It implies a read-only retrieval and specifies the date format, but says nothing about return contents, date-range validity, whether future dates are accepted, or rate limits. For a news-fetching tool with zero annotation coverage this is thin.

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, with the purpose stated before the argument spec. The bilingual duplication ('获取核心资讯' / 'Get core market news') is mildly redundant but not costly given the overall brevity.

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?

An output schema exists, so return values need not be explained. For a one-parameter retrieval tool this is close to adequate, but the ambiguity of 'core news' against four sibling news tools, and the unclear semantics of the date (is it a retrieval day? a filter?) leave real gaps.

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 description coverage is 0%, so the description must compensate, and it does: it names the date parameter, its type, the YYYYMMDD format, and gives a concrete example ('20260818'). That fully documents the single required parameter, exceeding the schema's bare 'string' declaration.

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

Purpose3/5

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

The description states a clear verb+resource ('Get core market news'), so the agent knows it retrieves news. However, 'core' is undefined and nothing distinguishes it from siblings like ChDomesticNews, ChGlobalNews, or ChOptionNews, which likely retrieve overlapping content. An agent cannot confidently pick this over those alternatives.

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 guidance on when to use this tool versus the many other news tools in the sibling list. The only operational hint is the date format, which is a parameter detail rather than usage context. The agent must infer the selection criteria entirely.

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