gangtise_one_pager
Generate a one-page AI investment summary for any A-share or Hong Kong stock, returned as Markdown.
Instructions
生成指定证券的 AI 一页纸投资摘要,返回 Markdown 内容。
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| securityCode | Yes | A 股或港股证券代码 |
Generate a one-page AI investment summary for any A-share or Hong Kong stock, returned as Markdown.
生成指定证券的 AI 一页纸投资摘要,返回 Markdown 内容。
| Name | Required | Description | Default |
|---|---|---|---|
| securityCode | Yes | A 股或港股证券代码 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits. It indicates the tool returns Markdown content, implying a read operation without side effects, but fails to disclose whether it caches data, requires authentication, or any other behavioral nuances. The description is minimally adequate but lacks depth.
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 in Chinese that efficiently conveys the core purpose and output format. Every word is necessary, and the structure is front-loaded with the action.
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?
With one simple parameter and no output schema, the description provides sufficient context for the tool's role. It differentiates well among many siblings. Minor omission: it does not explicitly state the security types beyond what the parameter description says, but overall it is 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?
Schema coverage is 100% because the single parameter 'securityCode' has a description in the schema ('A 股或港股证券代码'). The tool description adds no additional meaning beyond what the schema already provides, so baseline score of 3 applies.
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 tool generates an AI one-page investment summary for a specified security and returns Markdown content. It uses a specific verb ('生成'/generate) and resource ('投资摘要'/investment summary), and the distinct output format differentiates it from siblings like financial reports or announcements.
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 implies the tool is for generating a concise investment summary but provides no explicit guidance on when to use it versus alternatives like research reports, foreign opinions, or other listing tools. No when-to-use or when-not-to-use cues are given.
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/gangtiser/gangtise-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server