Skip to main content
Glama
taux-io

TWSE OpenAPI MCP Server

by taux-io

twse_realtime_quote

Fetch real-time stock quotes for Taiwan Stock Exchange (TSE) and over-the-counter (OTC) markets with approximately 5-second updates. Provide stock codes and market type.

Instructions

取得盤中即時報價(約 5 秒更新一次)。

OpenAPI 只有前一交易日資料,要當下的價格得走基本市況報導站。 ETF 與上市股票用 market="tse",上櫃用 "otc"。

Args: codes: 代號清單,例如 ["0050", "0056", "2330"]。 market: "tse"(上市)或 "otc"(上櫃)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codesYes
marketNotse

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations present, so description carries full burden. Discloses update frequency and data source (basic market station vs OpenAPI). Lacks details on rate limits, authentication, or error handling.

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?

Concise three-sentence description plus an Args block. Efficiently conveys purpose, usage, and parameters. Could be slightly more streamlined but minimal waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with output schema, description covers purpose, usage, parameters, and update frequency. No need to detail return values. Adequately complete.

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 0%, but description adds meaning: codes are stock symbols with examples, market is exchange type with default. Compensates for missing schema descriptions.

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?

Description clearly states it retrieves real-time stock quotes with approx 5-second updates, contrasting with OpenAPI's previous-day data. It distinguishes from sibling tools (datasets, ETF snapshot) by focusing on real-time quotes.

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 context for when to use (real-time vs historical), and guidance on market parameter (tse vs otc). Does not explicitly exclude alternatives or mention when not to use, but context suffices.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taux-io/twse-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server