Skip to main content
Glama

台股題材與高股息

列出台股四個 AI 題材

list_stock_themes
Read-onlyIdempotent

列出台股四個 AI 題材(AI 伺服器供應鏈、半導體先進製程與封裝設備、液冷散熱、CPO 共同封裝光學)的成分股數與今日漲跌摘要。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_stock_themes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds genuine value by specifying the returned content and that the change data is '今日' (today's), signaling freshness, but with no output schema present it stops short of describing the response shape or whether all four themes are always returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the parenthetical enumeration earns its length by pinning down the fixed theme set the zero-parameter tool always operates on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description must carry the return-value burden, and it does so by naming the two returned measures (constituent counts and today's change summary). It is slightly thin on how the four themes are structured in the response, but nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The description correctly implies a fixed, non-configurable scope by enumerating exactly which four themes are returned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('列出') with a bounded resource (the four named AI themes) and states what is returned (constituent counts and today's gain/loss summary). It does not, however, distinguish itself from the sibling get_theme_stocks, leaving the agent to infer the boundary between theme summary and theme constituents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: by declaring it returns only counts and a daily change summary, an agent can infer this is an overview tool rather than a per-stock lookup. There is no explicit when-to-use, when-not-to-use, or named alternative such as get_theme_stocks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources