Skip to main content
Glama
tw-stock-mcp

tw-stock-mcp

by jiawei-hong

Get end-of-day TWSE market overview

get_market_overview
Read-onlyIdempotent

Get a one-call end-of-day Taiwan stock market brief with TAIEX and key indices, ranked sector performance, market breadth, turnover, and institutional net buy/sell for any trading day.

Instructions

One-call end-of-day brief of the Taiwan Stock Exchange (TWSE) for a trading day: TAIEX (加權指數) and key indices, sector indices (類指數) ranked by change, market breadth (advancers/decliners, limit up/down), turnover, and institutional investors' net buy/sell in TWD. Use get_market_index for intraday index values (including the TPEx index) and get_market_movers for the stocks behind the moves. Without date, uses the most recent trading day with published data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_market_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoTrading date YYYY-MM-DD. Default: latest available.
sectorsNoAll sector indices, or only the 5 best and 5 worst (default "top_bottom").

Output Schema

NameRequiredDescriptionDefault
dateYes
notesYes
breadthYesCommon stocks only
sectorsYesSorted by change_percent, best first
turnoverYesTWD by category: total = stocks + etf + warrants + other (TDRs, innovation board, ETNs, ...)
key_indicesYes
institutionalYesTWSE net buy/sell in TWD; null if not published yet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds genuinely new behavior: the date default resolves to the most recent trading day *with published data*, telling the agent the tool will not fail on a holiday or pre-publication day. It stops short of describing pagination, latency, or what happens with partially published data, so not a 5.

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

Conciseness5/5

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

Front-loaded with the payload contents, then routing, then the default. Every sentence carries distinct information — no restatement of the title, no filler.

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?

Output schema covers return values, annotations cover safety, schema documents both parameters. The description fills the remaining gaps: scope, sibling routing, and default-date behavior. Nothing an agent needs to call this correctly is 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 baseline is 3. The description still adds meaning by clarifying that an omitted `date` resolves to the most recent *trading* day with published data, disambiguating calendar-day vs trading-day semantics that the schema's 'latest available' leaves fuzzy. The `sectors` enum is left entirely to the schema, which is acceptable at full coverage.

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 ('One-call end-of-day brief of the Taiwan Stock Exchange') and enumerates the exact payload: TAIEX, sector indices ranked by change, breadth, turnover, institutional net buy/sell. An agent can distinguish it from get_market_index and get_market_movers 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?

Explicitly routes away from two named alternatives with the condition that selects each: get_market_index for intraday index values, get_market_movers for the individual stocks behind the moves. The implicit use case (end-of-day summary) is also stated.

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