Skip to main content
Glama

Taiwan stock: daily prices and chips

tw_get_daily_trading
Read-onlyIdempotent

Daily trading data of one Taiwan stock or ETF, newest day first (since 2021): price (open, high, low, close, change, volume, turnover; raw prices not adjusted for dividends, null on days without a trade), institutional (net buying by the three institutional investor types: foreign_* is foreign and mainland Chinese investors excluding foreign-owned dealers, trust_* investment trusts, dealer_* dealers' proprietary trading and hedging, total_net all three), margin (margin purchases and short sales with balances and limits), securities_lending (short sales of borrowed securities) and foreign_holding (shares issued, foreign holding and its percent, room left and the legal limit). All counts are shares (the exchanges publish margin data in lots; converted). Taiwan daily prices are government open data. Quotes and institutional data arrive at about 5:30 PM Taiwan time; margin, securities lending and foreign holding data at about 10:30 PM, so on the latest day those parts can be null (note says so). change_pct is calculated by Livermore. tw_list_institutional_ranking ranks the whole market. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesTaiwan stock code, e.g. 2330 (TSMC), 0050 (an ETF) or 00981A. Lowercase, 2330.TW and 2330.TWO also work. Use tw_search to find a code by company name.
daysNoNumber of trading days, newest first (1-200, default 20). Data starts in 2021.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe chips page on tw.livermore.club (Traditional Chinese).
codeYes
nameYesShort name in Traditional Chinese.
noteYes
rowsYes
marketYesTWSE = listed on the Taiwan Stock Exchange; TPEx = traded on the Taipei Exchange (OTC market).
name_enYesEnglish short name (for example TSMC); null when there is none.
currencyYesEvery amount of money in this result is in New Taiwan dollars (TWD).
attributionYesRequired 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.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description adds substantial behavior the annotations cannot convey: data-arrival timing (quotes/institutional ~5:30 PM, margin/lending/foreign-holding ~10:30 PM Taiwan time), resulting nulls on the latest day, raw unadjusted prices and nulls on non-trading days, lot-to-share conversion, and the attribution/computed_by_livermore provenance requirement.

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?

It is front-loaded with purpose and the body is dense but almost every sentence carries operational value (timing, units, conventions, attribution). The trade-off is a single ~200-word paragraph for a two-parameter tool, which hurts scanability even though little is truly filler.

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?

Given an available output schema, the description still supplies everything needed to call and interpret the tool: units (TWD, shares, _pct = percent), market codes (TWSE/TPEx), language and url caveats, null conditions, and licensing obligations. Nothing an agent needs to invoke it correctly is missing.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented in the schema (code formats and the days range/default). The description reinforces ordering ('newest day first') and the 2021 start, but adds no syntax or format detail beyond the schema — the baseline of 3 is appropriate when the schema does the heavy lifting.

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?

The opening sentence names a specific verb/resource and scope: 'Daily trading data of one Taiwan stock or ETF, newest day first (since 2021)'. It enumerates exactly what data groups are returned (price, institutional, margin, securities_lending, foreign_holding) and explicitly differentiates from the sibling tw_list_institutional_ranking, which 'ranks the whole market'.

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

Usage Guidelines4/5

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

It gives clear context for when this tool is the right one (single-stock daily price + chips data) and points at tw_list_institutional_ranking for market-wide ranking, plus the schema directs users to tw_search for code lookup. However, it never states exclusions against the other single-stock siblings (tw_get_stock, get_stock) or a 'do not use for X' caveat, so guidance is clear but not explicit about alternatives.

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