taiwan-stock-mcp

get_quote

Retrieve an uncached TWSE/TPEx quote by code, returning TWD price, change, lots, and five bid/ask levels; market detection and freshness fields support reliable interpretation.

Instructions

Get an uncached TWSE/TPEx quote by code, TWD price, change, lots and five bid/ask levels.

Market is detected automatically. Closed sessions retain the last trade and its actual date/time; missing MIS trades use the labelled daily close. Realtime requests are paced to at most one per second. Check as_of and price_basis before interpreting freshness.

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": "get_quote"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	4-6 character TWSE/TPEx code, e.g. 2330 or 0050

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses uncached retrieval, automatic market detection, closed-session staleness semantics, the labelled daily-close fallback when MIS trades are missing, and a rate limit of one realtime request per second. Only error/failure behavior for bad codes is undisclosed. A genuinely informative description for an unannotated read tool.

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 purpose is front-loaded in the first clause, then each subsequent sentence adds one distinct operational fact (market detection, closed-session dating, daily-close fallback, pacing, freshness fields). No sentence is redundant or restates the schema.

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?

With an output schema present, the description need not explain return values, and it correctly spends its words on freshness semantics and pacing instead. The remaining gap is error handling for unknown or malformed codes, which matters for a single-parameter lookup that can fail cleanly.

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?

There is a single required parameter whose schema description already covers the format ('4-6 character TWSE/TPEx code, e.g. 2330 or 0050') at 100% coverage, so the schema does the heavy lifting. The description adds only that market is inferred from the code rather than supplied. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Get an uncached TWSE/TPEx quote by code') and even enumerates the returned fields (TWD price, change, lots, five bid/ask levels), so the agent knows exactly what it retrieves. It does not name the sibling tools (scan_market, screen_valuation), but the single-instrument scope implicitly separates it from the screening tools. Clear, just short of explicit sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'by code' and the freshness caveats, but the description never states when to reach for this over the sibling screening tools, nor what to do when a code is invalid or the market is ambiguous. The pacing rule ('at most one per second') is the closest thing to operating guidance and is about the call pattern rather than tool choice.

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

Deploy Server