全球财经快讯
stock_news_globalRetrieve real-time global financial news to track market developments and support investment decisions.
Instructions
获取最新的全球财经快讯
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
stock_news_globalRetrieve real-time global financial news to track market developments and support investment decisions.
获取最新的全球财经快讯
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description does not disclose any behavioral traits such as the number of items returned, frequency of updates, or source of news. The minimal description fails to inform the agent about what to expect.
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 concise sentence with no extraneous information. Every word contributes to the purpose.
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 that there are no parameters and no output schema, the description is minimally complete. However, it lacks details such as the number of results or content format, which would be helpful for the agent.
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 has no parameters, so schema coverage is 100%. The description adds meaning by clarifying that the tool retrieves global financial news, which is sufficient for a parameterless tool.
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 ('获取' meaning 'get') and resource ('全球财经快讯' meaning 'global financial news flashes'). It distinguishes from sibling tools like 'stock_news' (likely stock-specific) and 'stock_news_us' (US-specific) by focusing on global financial news.
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?
No guidance is provided on when to use this tool versus alternatives like 'stock_news' or 'stock_news_us'. There is no context about prerequisites or exclusions.
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