Skip to main content
Glama

台股題材與高股息

台股即時行情

get_tw_market_quotes
Read-onlyIdempotent

台股即時行情:加權指數、櫃買指數、權值股與熱門 ETF(證交所基本市況報導,盤中即時、可能略有延遲)。可指定任意台股代號(含上櫃、ETF)。

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_tw_market_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
codesNo台股代號,例:["2330","0050"];不填回傳大盤與熱門股

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's value-add is the data provenance and freshness caveat: TWSE 基本市況報導 with intraday data that 可能略有延遲. That latency disclosure is exactly the kind of trait annotations cannot express. It stops short of describing response shape or per-code error behavior.

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?

One front-loaded sentence, no filler, with coverage scope first and the qualifier about latency folded into a parenthetical. Nothing here could be removed without losing information.

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 no output schema, the description does well to establish source, freshness, default scope and accepted code universe for a simple one-parameter read tool. The remaining gap is the shape of the return payload (fields, ordering when multiple codes are passed), which an agent must discover by calling.

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% and the single optional parameter already documents the format and the empty-case default. The description adds only one genuinely new constraint, that 上櫃 codes and ETFs are accepted, so the schema still carries most of the semantic load.

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 plus resource ('台股即時行情') and enumerates coverage precisely: TAIEX, OTC index, weighted stocks, popular ETFs, plus arbitrary TW tickers. The Taiwan-equity scope plus OTC/ETF inclusion clearly separates it from get_us_quotes and from the dividend/chip siblings.

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?

The default behavior when no codes are supplied (return market-wide and popular stocks) is stated, which gives implied usage guidance. However, there is no explicit when-to-use/when-not framing, no mention of prerequisites, and no reference to a related sibling (e.g. individual stock fundamentals) that would route the agent away from this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources