OneQAZ Trading Intelligence

Position Detail

get_position_detail

Read-onlyIdempotent

Purpose: Per-symbol paper position deep-dive (position + recent trades + decisions). Triggers (casual questions too): "how's the BTC position doing?", "삼성전자 얼마나 벌고 있어?", "why are you holding X?", "그 종목 지금 수익률 어때?", "tell me about the AAPL position". When to call: full context for one ticker. Prerequisites: confirm the symbol holds a position via get_positions. Next steps: get_signal_detail, get_role_analysis. Caveats: returns an error envelope when no position exists for the symbol.

Input Schema

TableJSON Schema

Name	Required	Description
`coin`	No	Legacy alias of symbol (kept for backward compatibility)
`symbol`	No	Asset identifier (preferred; e.g., BTC, ETH, AAPL)
`market_id`	Yes	Market ID (crypto, kr_stock, us_stock; aliases coin/kr/us accepted)

Output Schema

TableJSON Schema

Name	Required	Description
`full_data`	No
`timestamp`	Yes	RFC3339 UTC, server build time
`disclaimer`	Yes	Canonical compliance disclaimer (always present)
`request_id`	Yes	32-hex per-response correlation id
`is_real_money`	No
`data_classification`	No
`is_investment_advice`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed2 schema fields changedSep 23, 2026

addedOutput schema / properties

Added value: +{
+  "data_classification": {
+    "anyOf": [
+      {
+        "const": "research_information_only",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "disclaimer": {
+    "description": "Canonical compliance disclaimer (always present)",
+    "type": "string"
+  },
+  "full_data": {
+    "anyOf": [
+      {
+        "additionalProperties": true,
+        "description": "`full_data` for get_position_detail — 실응답에서 추출(2026-09-23).",
+        "properties": {
+          "coin": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "market_id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "position": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "recent_decisions": {
+            "items": {},
+            "type": "array"
+          },
+          "recent_trades": {
+            "items": {},
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "is_investment_advice": {
+    "anyOf": [
+      {
+        "const": false,
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "is_real_money": {
+    "anyOf": [
+      {
+        "const": false,
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "request_id": {
+    "description": "32-hex per-response correlation id",
+    "type": "string"
+  },
+  "timestamp": {
+    "description": "RFC3339 UTC, server build time",
+    "type": "string"
+  }
+}

addedOutput schema / required

Added value: +[
+  "disclaimer",
+  "request_id",
+  "timestamp"
+]

Changed4 schema fields changedSep 22, 2026

addedInput schema / properties / coin / description

Added value: +"Legacy alias of symbol (kept for backward compatibility)"

addedInput schema / properties / market_id / description

Added value: +"Market ID (crypto, kr_stock, us_stock; aliases coin/kr/us accepted)"

addedInput schema / properties / market_id / enum

Added value: +[
+  "crypto",
+  "kr_stock",
+  "us_stock"
+]

addedInput schema / properties / symbol / description

Added value: +"Asset identifier (preferred; e.g., BTC, ETH, AAPL)"

Changed5 schema fields changedJul 7, 2026

addedInput schema / properties / coin / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / coin / default
```
Added value: +null
```
removedInput schema / properties / coin / type
```
Removed value: -"string"
```

addedInput schema / properties / symbol

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

changedInput schema / required

Previous value: -[
-  "market_id",
-  "coin"
-]New value: +[
+  "market_id"
+]

First observedApr 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered structurally. The description adds real behavioral context beyond them by stating it returns an error envelope when no position exists for the symbol, which tells the agent to expect a failure path rather than empty data.

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?

Labeled sections (Purpose, Triggers, When to call, Prerequisites, Next steps, Caveats) front-load the essential meaning and are easy to scan. The multilingual trigger examples add length but earn their place by improving intent matching.

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?

For a one-ticker read tool with an output schema and read-only annotations, the description supplies everything the agent still needs: what is returned, the pre-check step, follow-on tools, and the no-position error case.

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 description coverage is 100%, so coin/symbol/market_id and the enum aliases are already documented in the schema; the baseline of 3 applies. The description adds only an indirect hint that the tool is keyed to a single ticker, with no extra syntax or format guidance for market_id.

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 first line names a specific verb-scoped resource: a per-symbol position 'deep-dive' returning position, recent trades, and decisions. This distinguishes it cleanly from get_positions (list) and get_trade_history / get_latest_decisions, which return only one slice of that data.

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?

Explicitly gives triggers including casual utterances ('why are you holding X?'), the selection condition ('full context for one ticker'), a prerequisite (confirm the position exists via get_positions), and follow-on tools (get_signal_detail, get_role_analysis). Nothing about when to use it versus alternatives is left implicit.

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

All OneQAZ Trading Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.