Skip to main content
Glama
tw-stock-mcp

tw-stock-mcp

by jiawei-hong

Get a one-call stock overview

get_stock_overview
Read-only

Get one Taiwan stock's quote, one-month price summary, fundamentals, institutional trading, and event window in a single call; use it for a stock-specific overview.

Instructions

Everything about one Taiwan stock in a single call: the latest quote, a rolling 1-month price summary, fundamentals (valuation, monthly revenue, latest income statement), the latest day of institutional trading (三大法人), and events from 14 days ago to 45 days ahead (ex-dividend, disposition, attention, halts; attention notices only exist for the latest trading day, see events_coverage). Use this first when asked about a specific stock; call the individual tools only for more detail (e.g. get_history for a longer window). Sections that fail to load are null and explained in warnings; the rest are still returned.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_stock_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketNoOmit to detect automatically.
symbolYesCode ("2330") or exact name ("台積電").

Output Schema

NameRequiredDescriptionDefault
codeYes
nameNo
quoteYesSame shape as a get_quote quote: volume is in lots for the regular session only, so it is lower than the end-of-day volume in shares.
eventsYes
marketNo
warningsYes
fundamentalsYesSame shape as a get_fundamentals company
institutionalYesNet shares by group for `date`, same shape as a get_institutional_trading row plus date
events_coverageNoDate range each event dataset contained (see get_market_events coverage). Attention notices cover the latest trading day only.
price_summary_1mYesSame shape as get_history summary for a rolling month ending today (not month-to-date; use get_history with start for that). change is from reference_close; average_daily_volume is in shares, total_turnover in TWD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: partial failures are returned as null sections explained in `warnings` while the rest of the response still loads, event coverage spans 14 days back to 45 days ahead, and attention notices are limited to the latest trading day. These details meaningfully inform how to interpret the result.

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?

The description is front-loaded with the core purpose and then provides usage guidance and failure/coverage details in just two dense sentences. Every clause earns its place, with no redundant or filler wording.

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 that an output schema exists, the description need not explain return values. It still fully covers what sections are included, how partial failures are surfaced, the event coverage window, and the attention-notice limitation, leaving no critical gaps for correct invocation.

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%, with both parameters fully documented in the input schema. The description adds no additional parameter meaning beyond what the schema already states, so the baseline score of 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?

The description states a specific verb and resource: a single-call overview of one Taiwan stock, enumerating exactly what is included (quote, price summary, fundamentals, institutional trading, events). It also distinguishes itself from sibling tools by telling the agent to use this first for a specific stock and to call individual tools only for more detail.

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 when-to-use guidance is given: 'Use this first when asked about a specific stock; call the individual tools only for more detail (e.g. get_history for a longer window).' It also clarifies that attention notices exist only for the latest trading day, preventing misinterpretation.

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