Skip to main content
Glama

Taiwan Market Open Data (Unofficial)

Futures contract snapshot

snapshot.futures
Read-onlyIdempotent

One TAIFEX futures contract for the latest trading day: open, high, low, close, change, volume, settlement and open interest for each contract month (regular and after-hours sessions), a near-month summary, institutional and large-trader positions, and final settlement prices. Accepts codes ("TX", "MTX") or Chinese names; an ambiguous name returns candidates only. Source: TAIFEX OAS; futures only; not live. 一個期貨契約(最新一個交易日)的完整概況:各月份的開高低收、漲跌、成交量、結算價、未平倉(一般與盤後時段)、近月摘要、三大法人部位(指數類期貨)、大額交易人部位與最後結算價。可用代號("TX"、"MTX"、"TMF"、"CDF")或名稱("台指期"、"小台"、"台積電期貨");名稱對到多個契約時只回 candidates,請向使用者確認再用代號重查。只含期貨;選擇權與整體期貨籌碼請用 dataset.search 或 snapshot.market。

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": {
      "contract": "<contract>"
    },
    "name": "snapshot.futures"
  }
}

Input Schema

NameRequiredDescriptionDefault
contractYes期貨契約代號或名稱,例如 "TX"、"小台"、"台積電期貨"。

Output Schema

NameRequiredDescriptionDefault
dateNo
nameYes
queryYes
quotesNo
sourceYes
caveatsYes
contractYes
candidatesNo
near_monthNo
institutionalNo
large_tradersNo
final_settlementNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / contract / maxLength
      Added value: +40
    • addedInput schema / properties / contract / minLength
      Added value: +1
  2. Changed6 schema fields changed
    • removedOutput schema / properties / contract / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / contract / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / date / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses data source (TAIFEX OAS), freshness (latest trading day, not live), and ambiguous-name behavior that returns candidates only. These are important behavioral traits an agent needs in order to call and interpret the tool correctly.

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

Conciseness3/5

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

The English portion is front-loaded and information-dense, but the entire description is duplicated in Chinese, roughly doubling length without adding new meaning for an agent. The result is clear but unnecessarily verbose due to bilingual repetition.

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?

The definition covers scope, data freshness, accepted input formats, ambiguity handling, included data sections, and when to use sibling tools for excluded data. Since an output schema exists, it does not need to explain returned values, and no important calling context appears 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 the baseline is 3, but the description adds useful semantics: it lists accepted code examples (TX, MTX, TMF, CDF), Chinese name examples, and explains what happens when a name maps to multiple contracts. This meaningfully extends the single parameter beyond its schema description.

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 names a specific resource (one TAIFEX futures contract), time scope (latest trading day), and the exact fields returned, including regular and after-hours sessions, positions, and settlement. It also distinguishes the tool from options and overall futures chip coverage by routing those to dataset.search or snapshot.market.

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?

The description gives clear usage context: futures only, not live, accepts codes or Chinese names, and ambiguous names return candidates for confirmation. It names alternatives for options and aggregate futures positioning data, but does not explicitly route live quote needs to quote.realtime despite flagging that this tool is not live.

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.