个股新闻
stock_newsRetrieve recent news for a given stock symbol to track company updates and market sentiment.
Instructions
获取指定个股最近新闻动态
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 返回数量(int) | |
| symbol | Yes | 股票代码 |
stock_newsRetrieve recent news for a given stock symbol to track company updates and market sentiment.
获取指定个股最近新闻动态
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 返回数量(int) | |
| symbol | Yes | 股票代码 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states that recent news is fetched, with no disclosure of return format, pagination, rate limits, or side effects. The behavior is implied to be read-only but not explicitly confirmed.
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, efficient sentence that immediately conveys the tool's function. There is no redundant or filler content.
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?
For a simple two-parameter tool, the description is present but minimal. It does not explain what the returned news contains (e.g., article titles, timestamps, links), which might be useful, but the schema covers parameters and the tool's simplicity mitigates the gap.
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 input schema covers all parameters with descriptions (100% coverage), so the baseline is 3. The description adds no additional meaning beyond what the schema already provides; limit is described as '返回数量' in the schema, and symbol is just '股票代码'.
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 states the action (获取/get) and the target (指定个股最近新闻动态/recent news for a specified stock), with the scope '指定个股' distinguishing it from the global news sibling tool stock_news_global. This is a specific and unambiguous purpose.
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?
There is no guidance on when to use this tool versus alternatives. The description only states the basic function without mentioning exclusions, prerequisites, or alternative tools such as stock_news_global.
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/tchivs/aktools-pro'
If you have feedback or need assistance with the MCP directory API, please join our Discord server