A股市场PE分位
stock_market_pe_percentileGet historical percentile of A-share market PE/PB to evaluate overall market valuation levels.
Instructions
获取A股市场整体PE/PB的历史分位数,用于判断市场整体估值水平。
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
stock_market_pe_percentileGet historical percentile of A-share market PE/PB to evaluate overall market valuation levels.
获取A股市场整体PE/PB的历史分位数,用于判断市场整体估值水平。
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only states '获取' (get) without mentioning data source, update frequency, safety (read-only), or any side effects. This lacks critical transparency for an agent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that efficiently communicates the tool's purpose and usage. No redundant or unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description does not explain return values or format. While the tool is simple (no params), an agent might benefit from knowing the output structure. It is minimally adequate but not complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and schema coverage is 100% (trivial). Baseline score is 4; the description does not need to add parameter details. It correctly implies no inputs are required.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies the tool retrieves historical PE/PB percentiles for the A-share market to assess overall valuation. The title and description align, and it is distinct from sibling tools like stock_industry_pe (industry-level) and stock_indicators (individual stock).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions the purpose ('用于判断市场整体估值水平') but does not explicitly state when to use this tool versus alternatives. No exclusions or alternative tool references are provided, leaving usage context implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/openstockdata/stock-data-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server