Stockfacts

Search Taiwan stocks

tw_search

Read-onlyIdempotent

Find Taiwan stocks and ETFs listed on TWSE or TPEx (still trading) by code, Chinese short or full name, or English name; start here to get the code every other tw_ tool takes (TSMC is 2330). Matching runs in tiers: exact code, code prefix, exact short name, short name prefix, short name contains, then full name or English names contain (queries of at least 2 characters); within a tier companies come before ETFs and other securities, then larger market caps first. 2330.TW and 2330.TWO are read as the code. Each result has code, name and full_name (Traditional Chinese), name_en, market (TWSE or TPEx), kind (stock, etf, other) and url. Follow up with tw_get_stock. Taiwan stocks are separate from the US tools (search, get_stock); TSMC's US ADR is TSM there. Taiwan conventions: money is in New Taiwan dollars (currency TWD), share counts are in shares (1 lot = 1,000 shares), prices are in TWD and fields ending in _pct are percentages (12.5 means 12.5%). market is TWSE (listed) or TPEx (OTC). Names are in Traditional Chinese, with name_en where available. url links to tw.livermore.club, whose pages are in Traditional Chinese only. Keep attribution when you present the data: Taiwan's Open Government Data License requires naming its sources, and fields listed in computed_by_livermore are Livermore's calculations, not official figures.

Tool call template

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": {
      "query": "<query>"
    },
    "name": "tw_search"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum matches (1-50, default 10).
`query`	Yes	A code (2330, 2330.TW), a Chinese short or full company name, or an English name (TSMC, Taiwan Semiconductor).

Output Schema

Name	Required	Description
`query`	Yes	The query as searched (spaces collapsed; a .TW or .TWO suffix removed).
`results`	Yes
`currency`	Yes	Every amount of money in this result is in New Taiwan dollars (TWD).
`attribution`	Yes	Required attribution: Taiwan's Open Government Data License requires naming the sources when you present or pass on this data, and Livermore's own calculations must be kept apart from the official figures.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover only the safety profile (readOnly/idempotent/non-destructive), so the description carries the rest and does so richly: tiered matching order, company-before-ETF and market-cap ordering within tiers, the 2-character minimum, code normalization (2330.TW/2330.TWO), and the fields each result carries. It also discloses the licensing/attribution obligation and that computed_by_livermore fields are not official figures, which no annotation conveys.

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

Conciseness4/5

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

Front-loaded with the core action, argument types, and follow-up tool in the first two clauses; the trailing conventions block (TWD, lots, _pct, Traditional Chinese, attribution) is long but each item is actionable for a Taiwan-market tool. Minor redundancy in enumerating result fields that the output schema already defines.

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

Completeness5/5

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

With an output schema present, the description need not explain return values, yet it still frames them usefully. Combined with the routing guidance, currency/unit conventions, and attribution requirement, an agent has everything needed to call and correctly present results from this tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics beyond the schema: query normalization rules, the 2-character threshold for name matching, and the tier hierarchy that determines which matches win. It does not restate the limit bounds, which is fine since the schema does.

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

Purpose5/5

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

States a specific verb+resource+scope: find Taiwan stocks and ETFs listed on TWSE or TPEx that are still trading, by code, Chinese short/full name, or English name. It explicitly positions itself as the entry point that produces the `code` consumed by every other tw_ tool, which cleanly separates it from tw_get_stock and from the US `search`/`get_stock`.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('start here to get the code every other tw_ tool takes'), a named follow-up (tw_get_stock), and active exclusions ('Taiwan stocks are separate from the US tools (search, get_stock); TSMC's US ADR is TSM there'). An agent has no ambiguity about routing.

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

All Stockfacts tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?