Stockfacts

Taiwan stock: monthly revenue

tw_get_monthly_revenue

Read-onlyIdempotent

Monthly revenue of one Taiwan-listed company (TWSE or TPEx), newest month first: revenue, the previous month and the same month a year earlier, month-over-month, year-over-year and year-to-date changes, and company_note, the company's own explanation of the change (Traditional Chinese). Taiwanese companies report revenue every month, by the 10th of the following month; data starts in January 2013. The percentages are reported by the company through MOPS, not calculated by Livermore. ETFs and other securities have none (empty months with a note). Follow up with tw_get_financials for quarterly statements. 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

Name	Required	Description	Default
`code`	Yes	Taiwan 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.
`months`	No	Number of months, newest first (1-200, default 24). Data starts in January 2013.

Output Schema

Name	Required	Description
`url`	Yes	The revenue page on tw.livermore.club (Traditional Chinese).
`code`	Yes
`name`	Yes	Short name in Traditional Chinese.
`note`	Yes
`market`	Yes	TWSE = listed on the Taiwan Stock Exchange; TPEx = traded on the Taipei Exchange (OTC market).
`months`	Yes
`name_en`	Yes	English short name (for example TSMC); null when there is none.
`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.
`earliest_month`	Yes
`available_months`	Yes	Months of revenue Livermore has for this company.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026

TDQS

A4.6/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 behavioral context beyond them: data starts January 2013, reporting deadline (by the 10th of the following month), that percentages are company-reported through MOPS rather than calculated by Livermore, ETF behavior (empty months with a note), and the attribution obligation under Taiwan's Open Government Data License.

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?

Dense but front-loaded: the core purpose and return shape come first, followed by reporting cadence and conventions. The Taiwan-conventions paragraph is lengthy but every clause carries operational meaning (units, currency, naming, attribution).

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?

An output schema exists so return values need not be explained, yet the description still covers units, currency, naming language, attribution requirements, data start date, and the natural follow-up tool. Nothing needed to call it correctly appears to be 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 real semantic context for both parameters: it clarifies the data starts January 2013 (which bounds `months`), and explains the market/code conventions and TWD/percentage units that govern interpretation of `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+resource ('Monthly revenue of one Taiwan-listed company (TWSE or TPEx)') with exact field scope: revenue, MoM, YoY, YTD, and company_note. It is clearly distinguishable from the many sibling tools, and explicitly names tw_get_financials as the quarterly counterpart.

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?

Provides clear usage context: follow up with tw_get_financials for quarterly statements, and note that ETFs have no revenue data. It does not, however, state explicit exclusions against other sibling tools (e.g., tw_get_daily_trading) or when this tool would be the wrong choice.

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?