Stockfacts

Taiwan industry value chains

tw_get_industry_chain

Read-onlyIdempotent

Taiwan's industry value chains from the TPEx Industry Value Chain Information Platform (47 chains such as semiconductors, D000), to find companies by what they do. Without chain: every chain with its code, name and number of companies (all, and TWSE/TPEx-listed). With chain: the chain's segments in platform order (stream upstream, midstream, downstream or another group; sub-segments carry parent_code) with up to limit companies each: TWSE and TPEx companies by market cap (latest close times shares issued, calculated by Livermore) with close and change, then emerging-market (ESB) and GISA companies, which have no stock page or quotes. With chain and segment: only that segment and its sub-segments. Unknown codes return an error. Names, streams and listing groups are in Traditional Chinese. The chain data is not government open data (attribution.other_sources); quotes are. tw_get_stock shows the segments of one company. 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

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": "tw_get_industry_chain"
  }
}

Input Schema

Name	Required	Description
`chain`	No	Industry chain code, e.g. D000 (semiconductors). Omit to list every chain.
`limit`	No	Companies per segment (1-200, default 10), listed companies by market cap first.
`segment`	No	A segment code within the chain, e.g. D300; returns that segment and its sub-segments. Needs chain.

Output Schema

Name	Required	Description
`url`	Yes
`chain`	Yes
`chains`	Yes	Every chain, when chain is not given.
`currency`	Yes	Every amount of money in this result is in New Taiwan dollars (TWD).
`segments`	Yes	The chain's segments in platform order (top-level segments, then their sub-segments), when chain is given.
`data_date`	Yes	The trading day of the closes and market caps.
`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 already cover safety (readOnly/idempotent/non-destructive), yet the description goes well beyond them: it discloses the data source and licensing obligations, distinguishes government open data from Livermore-computed fields (computed_by_livermore), specifies ordering rules (listed by market cap, then ESB/GISA which lack quotes), currency/unit conventions, and error behavior for unknown codes.

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?

Purpose and the three modes are front-loaded and every clause carries information, but the single dense paragraph mixes tool-specific behavior with a generic 'Taiwan conventions' block that reads as boilerplate appended across the tw_ family, making it heavier than strictly necessary.

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 document return values, and it still covers scope, all three modes, ordering, localization (Traditional Chinese names/streams), attribution requirements, and error semantics. Nothing an agent needs 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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema: it explains how `chain` and `segment` interact to change the result shape, that `limit` applies per segment with listed companies ordered first, and that sub-segments carry parent_code.

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 (get) and resource (Taiwan's industry value chains from the TPEx platform), gives a concrete scope example (47 chains, semiconductors, D000) and the core use case ('to find companies by what they do'). It is clearly distinguishable from sibling tw_get_stock, which it explicitly names as the per-company counterpart.

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?

Enumerates all three invocation modes and their distinct outputs: no chain (all chains with code, name, company counts), chain (segments in platform order with companies), and chain+segment (segment plus sub-segments only). It also routes to the alternative (tw_get_stock shows the segments of one company) and notes that unknown codes return an error.

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?