getETFRanking
Retrieve the top-ranked ETFs by regular investment account holdings on the Taiwan Stock Exchange.
Instructions
Get top ETFs by regular investment accounts
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Retrieve the top-ranked ETFs by regular investment account holdings on the Taiwan Stock Exchange.
Get top ETFs by regular investment accounts
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only restates the name's implication ('Get top ETFs...') without disclosing data freshness, scope, limitations, or any other behavioral traits. This is insufficient for a tool with no output schema or annotations.
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 very concise (one sentence) and front-loaded. However, it could be slightly more informative without losing conciseness, e.g., specifying the ranking metric or output type.
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 the tool has no parameters and no output schema, the description is minimal. It describes the input (none) but not the output structure or behavior. For a simple tool, it is barely adequate but lacks completeness regarding return format or data interpretation.
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 tool has no parameters, and the schema coverage is trivially 100%. The description adds no parameter information but is not required to do so. Baseline score of 4 is appropriate.
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 it gets top ETFs by regular investment accounts, providing a specific verb and resource. However, 'top' is vague and could mean different rankings (e.g., by volume, performance), and it does not distinguish from sibling tools that also provide rankings or financial data.
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 on when to use this tool versus alternatives. With sibling tools like getTop20Volume and getTopForeignHoldings, the description does not clarify why getETFRanking is preferable or what differentiates it.
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/pyang2045/twsemcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server