Stockfacts

Taiwan stock overview

tw_get_stock

Read-onlyIdempotent

Overview of one Taiwan stock or ETF (TWSE or TPEx) by code. security: names, market, kind, industry, listing and founding dates, chairman, president, website, auditor, main business (MOPS), shares outstanding and paid-in capital. quote: the latest trading day's close, change, volume and turnover with the P/E, P/B and dividend yield published by TWSE or TPEx (raw prices, not adjusted for dividends; Taiwan daily prices are government open data), plus change_pct and market_cap (close times shares issued) calculated by Livermore. latest_revenue: the latest month of revenue (see tw_get_monthly_revenue). latest_quarter: revenue, gross profit, operating income, net income attributable to the parent, EPS, margins, growth, ROE and debt ratio for the latest quarter (full statements in tw_get_financials). dividends: cash and stock dividends per share for the last 5 fiscal years (each year added up by Livermore) and the latest or upcoming ex-dividend date. intro: a company profile written by AI from the company's latest annual report (summary, products with revenue shares, markets, customers, suppliers, competitors, industry position, last year's results, outlook, milestones; Traditional Chinese). It may contain errors; the annual report's figures prevail (annual_report_url). industry_chains: the TPEx industry value chain segments the company belongs to, with up to 5 peers per segment by market cap (tw_get_industry_chain lists whole chains). production_sites: factories and other production sites researched by AI from public sources (status operating, under_construction or planned, location, coordinates and their precision, sources per site); coordinates with precision address, region or city come from OpenStreetMap and need the credit in coordinates_credit. urls: the overview, revenue, financials and chips pages. A part is null when there is no data: ETFs and other securities usually have only security, quote and dividends. For price history and daily institutional, margin, securities lending and foreign holding data use tw_get_daily_trading. 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": {
      "code": "<code>"
    },
    "name": "tw_get_stock"
  }
}

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.

Output Schema

Name	Required	Description
`urls`	Yes
`intro`	Yes
`quote`	Yes
`currency`	Yes	Every amount of money in this result is in New Taiwan dollars (TWD).
`security`	Yes
`dividends`	Yes
`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.
`latest_quarter`	Yes
`latest_revenue`	Yes
`industry_chains`	Yes
`production_sites`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: null semantics for missing data, the caveat that AI-written sections 'may contain errors' with annual_report_url as the authority, and a mandatory attribution/licensing requirement naming Taiwan's Open Government Data License. These are behavioral facts the agent cannot get from annotations or schema.

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

Conciseness3/5

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

Front-loaded with purpose and organized by output section, which aids scanning. However, the long field-by-field enumeration of the response duplicates what the output schema already provides, so a meaningful fraction of the ~350 words does not earn its place; it is thorough but over-long for a one-parameter tool.

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 output schema exists, the description need not restate return values, yet it still supplies the interpretive layer an agent needs: currency and unit conventions, percentage semantics, market codes (TWSE listed vs TPEx OTC), Traditional Chinese naming, and the attribution obligation. Nothing material 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% and the single `code` parameter is fully documented in the schema, including formats and the tw_search fallback. The description adds only the general Taiwan conventions block (TWD, lots of 1,000 shares, _pct fields), which is mostly about output interpretation rather than the parameter itself, so the baseline 3 is appropriate.

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 ('Overview of one Taiwan stock or ETF (TWSE or TPEx) by code') and immediately enumerates the data sections it returns, so the agent knows exactly what it gets. It also distinguishes itself from siblings by naming tw_get_daily_trading, tw_get_financials, tw_get_monthly_revenue and tw_get_industry_chain as the tools for adjacent data.

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?

Explicitly routes the agent: 'For price history and daily institutional, margin, securities lending and foreign holding data use tw_get_daily_trading', and defers full statements to tw_get_financials and whole chains to tw_get_industry_chain. It also notes the ETF edge case ('ETFs and other securities usually have only security, quote and dividends'), which is real when-to-use guidance.

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?