PandaStock

by D-Asce

Overview Schema Source Related Servers Discussions Admin

Python

Local

chAllMarketBearCompare

Compare bull/bear (long/short) sentiment across the whole market to assess overall market direction and balance.

Instructions

获取全市场多空对比。Get bull/bear (long/short) comparison of the whole market. No arguments.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.5Sep 27, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states there are no arguments and describes the scope, but omits whether this is a read-only snapshot, how fresh the data is, or any rate limits or side effects. For a market data retrieval tool, freshness and read-only nature are notable gaps.

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?

Two short sentences, front-loaded with the core purpose and immediately clarifying the argument situation. The bilingual phrasing is compact and every part earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (zero parameters) and the presence of an output schema, the description need not explain return values. It states the scope and that no arguments are required, which is sufficient for an agent to invoke it. The lack of any behavioral or usage context keeps it from a 5.

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?

The tool takes zero parameters, and the schema is empty. The description confirms 'No arguments,' matching the schema. With no parameters to document, the baseline of 4 is appropriate.

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 specific verb and resource: get bull/bear (long/short) comparison for the whole market. It is more specific than the tool name alone and distinguishes itself from sibling data tools by focusing on market-wide sentiment comparison. However, it does not explicitly differentiate itself from related market tools like ChMarketCurReal or ChMarketFundFlow.

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?

The description says 'No arguments' but provides no guidance on when to use this tool versus the many sibling market data tools. There are no conditions, prerequisites, or alternatives mentioned, leaving the agent to infer usage entirely from the name.

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