Skip to main content
Glama

Taiwan stock: financial statements

tw_get_financials
Read-onlyIdempotent

Financial statements of one Taiwan-listed company from the MOPS XBRL filings (since 2013 Q1), newest period first: period=quarterly (default) gives the latest 8 single quarters, annual the latest 5 fiscal years. Each period has income (revenue, cost_of_revenue, gross_profit, operating_expenses, operating_income, non_operating_income, net_interest_income and provision_expense for banks, pretax_income, tax_expense, net_income, net_income_parent, eps_basic, eps_diluted), balance (cash_and_equivalents, accounts_receivable, inventory, total_current_assets, ppe_net, total_assets, total_current_liabilities, borrowings, total_liabilities, share_capital, equity_parent, total_equity) and cash_flow (operating_cash_flow, capex, free_cash_flow, investing_cash_flow, financing_cash_flow, dividends_paid; capex and dividends_paid are positive), plus margins, yoy_pct, roe_pct and debt_ratio_pct calculated by Livermore. Amounts are TWD, EPS is TWD per share. Taiwanese companies file Q1-Q3 quarterly and Q4 only as the full year, so single-quarter Q4 (and Q2-Q3 for companies that file half-years) is derived by subtraction (income.derived), Q4 EPS is full-year EPS minus the first three quarters (eps_derived) and single-quarter cash flows are derived from year-to-date figures (cash_flow.derived). check_failed lists accounting identities that are off by more than 1%; the figures are shown as filed. Quarterly ROE is not annualized. template is the MOPS industry format: ci general companies, basi banks, bd securities firms, fh financial holding companies, ins insurers, mim other industries. Revenue means different things per template (operating revenue for ci; net revenue, i.e. net interest income plus other net revenue, for basi and fh; revenues for bd; income for mim; operating revenue for ins through 2025 and insurance revenue under IFRS 17 from 2026, which cannot be compared, so revenue growth across that change is null), so do not compare or rank revenue across templates. Fields a format does not have are null: banks, financial holding companies and insurers have no gross profit; banks and financial holding companies have no operating income; basi, fh and ins have no current assets, current liabilities, inventory or borrowings. note explains what applies to the company; ETFs and other securities have no statements (empty periods). 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.
periodNoquarterly (default): the latest 8 single quarters; annual: the latest 5 fiscal years.quarterly

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe financials page on tw.livermore.club (Traditional Chinese).
codeYes
nameYesShort name in Traditional Chinese.
noteYes
marketYesTWSE = listed on the Taiwan Stock Exchange; TPEx = traded on the Taipei Exchange (OTC market).
periodYes
name_enYesEnglish short name (for example TSMC); null when there is none.
periodsYes
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.2/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, idempotent), yet the description adds substantial beyond-annotation context: derived Q4/Q2-Q3 figures via subtraction, check_failed accounting identities, non-annualized quarterly ROE, template-specific field availability, per-template revenue definitions, and the attribution license requirement. This is exactly the kind of data-quality disclosure an agent needs.

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 purpose and period semantics, and nearly every clause carries information given the tool's complexity. However it is a single dense block with no structural separation, making it harder to scan than a tool this rich deserves.

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?

For a complex financial-statement tool with an output schema already present, the description is remarkably complete: units (TWD, EPS per share), share/lot conventions, market codes, name language, derived-field semantics, and attribution obligations are all covered.

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 description coverage is 100% and the period param's enum, default, and semantics are already documented in the schema, so the description largely restates them. It adds the ordering hint ('newest period first') but nothing else beyond what the schema provides for either parameter.

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 and resource ('Financial statements of one Taiwan-listed company from the MOPS XBRL filings') with explicit scope, source, and coverage window (since 2013 Q1). An agent can immediately tell this apart from tw_get_monthly_revenue, tw_get_daily_trading, or tw_get_stock without opening a schema.

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?

The description implies usage well (single-company statements, ETFs excluded, do-not-rank-revenue-across-templates) but never states when to pick this over siblings like get_financials or tw_get_monthly_revenue. It provides interpretation guidance rather than tool-selection guidance, so routing is left to inference.

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