取得某個台股題材的概念股名單：代號、名稱、上市或上櫃、在供應鏈做什麼、最新收盤價與漲跌幅，附分類依據出處。
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"theme": "<theme>"
},
"name": "get_theme_stocks"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| theme | Yes | ai-server、semi-equipment、liquid-cooling、cpo |
Changes observed during successful MCP inspections.
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 does disclose the shape of the returned data and notes that the classification is accompanied by its source (附分類依據出處), which is useful. It says nothing about data freshness, update cadence, coverage limits, or auth needs, which are the remaining behavioral gaps.
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?
A single dense sentence with the action front-loaded and the returned fields enumerated compactly. Nothing is redundant or padded.
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?
There is no output schema, and the description compensates well by listing exactly what comes back, including the supply-chain role and the classification source. Combined with the fully-covered enum parameter, an agent has enough to invoke it correctly; only freshness/scope caveats are absent.
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 description coverage is 100% and the single parameter is a fully enumerated 'theme' field. The description only restates that it takes a theme (某個台股題材) and adds no format or selection guidance beyond the schema, so the baseline 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 states a specific verb (取得) and resource (某個台股題材的概念股名單) and even enumerates the returned fields (代號、名稱、上市或上櫃、供應鏈角色、收盤價與漲跌幅). This clearly separates it from get_stock (single stock) and list_stock_themes (theme enumeration). It stops short of naming a sibling explicitly, so it does not reach the top tier.
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?
Usage is only implied: the single required 'theme' enum makes the intended call pattern apparent, and the description shows it retrieves the constituent list for one theme. There is no explicit when-to-use vs. list_stock_themes guidance, no prerequisite steps, and no exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.