Taiwan Market Open Data (Unofficial)

Market overview

snapshot.market

Read-onlyIdempotent

Whole-market overview for the previous trading day: TAIEX and its change, turnover, advancers and decliners, top 10 by volume, plus futures positioning (institutional net open interest, TAIEX futures positions, put/call ratio, large traders). scope="events" lists ex-dividend dates and shareholder meetings in the next two weeks and attention/disposition stocks. Every scope also includes a trading calendar: whether the market is open today and the next trading day (TWSE holiday schedule). Sources: TWSE OpenAPI and TAIFEX OAS; not live. 一次看完整體市場（前一交易日）：加權指數與漲跌、成交金額、上市股票漲跌家數、成交量前十名；以及期貨籌碼：三大法人期貨未平倉淨部位、台指期各法人部位、Put/Call 比、台指期大額交易人淨部位。只要其中一邊時用 scope="stock" 或 "futures"。scope="events" 另外列出全市場的近期事件：兩週內的除權除息與股東會、今天公布的注意股、處置中與即將處置的股票（皆為上市）；每個 scope 都附交易日曆：今天有沒有開盤、下一個交易日（證交所休市日表）。只問某一檔股票的除息、注意或處置狀態時，用 snapshot.stock。不含個別契約的行情價格；要查台指期、小台、個股期貨等單一期貨契約的收盤價與部位，用 snapshot.futures。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`scope`	No	"all"（預設，證券市場加期貨籌碼）、"stock"、"futures"，或 "events"（近期事件行事曆）。	all

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`source`	Yes
`caveats`	Yes
`交易日曆`	No
`期貨籌碼`	No
`證券市場`	No
`事件行事曆`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

addedOutput schema / properties / 交易日曆

Added value: +{
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}

AddedSep 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld). The description adds genuinely useful behavioral context beyond them: data is not live, reflects the previous trading day, and is sourced from TWSE OpenAPI and TAIFEX OAS — freshness is a critical trait for a market snapshot and is not derivable from annotations.

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 and well organized, but the entire content is duplicated verbatim in Chinese and English, roughly doubling length without adding new information for a single reader. The scope-specific guidance is somewhat interleaved with the content inventory, making it longer than 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 needn't explain return values, and annotations carry the safety profile. Combined with the inventory of returned data, freshness caveat, source attribution, and sibling routing, an agent has everything needed to select and call it correctly.

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% and the enum values are already documented in the schema, so baseline is 3. The description goes further by explaining what each scope actually contains (events lists ex-dividend dates, shareholder meetings, attention/disposition stocks) and that the trading calendar is included in every scope, which the schema does not convey.

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 resource and scope: whole-market overview for the previous trading day, enumerating exactly what it returns (TAIEX, turnover, advancers/decliners, top 10 by volume, futures positioning) plus scope-dependent additions. An agent can distinguish it from snapshot.stock and snapshot.futures without opening any schema.

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?

Explicit routing rules: use scope="stock" or "futures" when only one side is needed; use snapshot.stock for a single stock's ex-dividend/attention/disposition status; use snapshot.futures for individual futures contract prices and positions. Both the when and the when-not (不含個別契約行情價格) are stated with named alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Taiwan Market Open Data (Unofficial) 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.