Skip to main content
Glama

get_target_instrument_state

Fetch real-time state of the OSE Nikkei 225 micro futures contract, including micro settlement and role indicators, for market research.

Instructions

真正交易標的狀態(OSE_NIKKEI225_MICRO_FUTURES)+ Micro settlement + 角色標記。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

無任何註解,描述承擔全部行為揭露責任。描述僅列出狀態內容,但未說明此操作是否為唯讀、是否需要權限、是否有副作用,或失敗情境。工具名含有 get 暗示唯讀,但描述本身未確認,對代理的風險評估幫助有限。

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

Conciseness4/5

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

描述僅一句話,精簡無冗餘,核心資訊(標的、狀態項目)有呈現。但因過度精簡導致部分語意模糊(如「角色標記」的具體含義),結構上可接受,但前段「真正交易」語意略顯籠統。

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

對於 0 參數、無輸出 Schema 的工具,描述提供了基本標的資訊,但缺少使用時機、回傳格式和唯讀性質的說明。在兄弟工具眾多的環境中,描述未能充分幫助代理區分使用情境,屬於「最低可用但有明顯缺口」。

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 覆蓋率 100%,因此描述無需補充參數意義。基於 0 參數的基準,此維度不需扣分,描述中提到的 Micro settlement 和角色標記可視為回傳內容而非參數。

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?

描述明確指出具體的資源(OSE_NIKKEI225_MICRO_FUTURES)和狀態的組成(Micro settlement、角色標記),能與其他 get_* 工具區分。雖然沒有明確的動詞,但工具名稱已含 get,整體目的仍屬清晰,且非單純重述名稱。

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

Usage Guidelines2/5

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

描述完全沒有說明何時應使用此工具,也未提及與任何兄弟工具的替代關係或排除條件。'真正交易標的'暗示某種區分,但未具體說明,代理無法從中判斷與 get_market_data 或 get_data_source_status 的分工。

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