PandaStock

by D-Asce

Overview Schema Source Related Servers Discussions Admin

Python

Local

ChGlobalNews

Retrieve global financial news for a specified date (YYYYMMDD) to support market research and trading decisions.

Instructions

获取全球财经要闻。Get global financial 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": "ChGlobalNews"
  }
}

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

B3.1/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 burden, and it discloses essentially nothing beyond the surface purpose. It does not say whether this is a read-only fetch, how results are scoped or ordered, whether the date must be today/past, or any rate/availability limits.

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 a single terse line and front-loads the purpose before the argument note. The Chinese/English restatement is slightly redundant but adds negligible length.

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, and the single required parameter's format is covered. However, for a news-retrieval tool with many sibling news variants and zero annotations, the description is thin — no scope, ordering, or differentiation guidance for correct selection.

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% — the `date` property has no description in the schema — but the description compensates by giving the exact format 'YYYYMMDD'. That is the key semantic detail an agent needs and it is not available from structured data.

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?

The description states a clear verb+resource: retrieve global financial news ('获取全球财经要闻 / Get global financial news'). The word 'global' implicitly distinguishes it from sibling news tools like ChDomesticNews and ChCoreNews, but no explicit sibling differentiation is offered.

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 choose this tool over ChDomesticNews, ChCoreNews, or ChOptionNews, and no mention of prerequisites or date constraints. Only the argument format is given, which is parameter documentation rather than usage guidance.

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