OneQAZ Trading Intelligence

get_role_analysis

Read-onlyIdempotent

Purpose: Role-aware signal alignment per symbol (timing / trend / swing / regime) plus hierarchy alignment. Triggers (casual questions too): "is BTC bullish across timeframes?", "단기랑 장기가 같은 방향이야?", "multi-timeframe view for AAPL?", "시간대별 신호가 일치해?", "short-term vs long-term signal?". When to call: multi-timeframe analysis, cross-role agreement checks. Prerequisites: get_signal_detail recommended. Next steps: market://{market_id}/unified/symbol/{symbol}, get_position_detail. Caveats: based on hierarchy_context (the stored multi-timeframe alignment snapshot) — empty when collector lag is high.

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, AAPL)
`market_id`	Yes	Market ID (crypto, kr_stock, us_stock). Aliases coin/kr/us and any letter case are 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.

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_role_analysis — 실응답에서 추출(2026-09-23).",
+        "properties": {
+          "combined": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "hierarchy": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "market_id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "roles": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "symbol": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "timestamp": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          }
+        },
+        "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 and any letter case are 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, 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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description correctly avoids repeating those. It adds a valuable caveat: results depend on a stored hierarchy_context snapshot and may be empty when collector lag is high. This discloses a data-freshness dependency beyond the structured metadata, though it doesn't cover auth or rate limits (not critical for this read-only tool).

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?

The description is neatly organized into labeled sections (Purpose, Triggers, When to call, Prerequisites, Next steps, Caveats) that front-load the core purpose. Each section earns its place, though the trigger list with four example questions is slightly longer than necessary. Overall, it is efficient and scannable.

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 read-only analysis tool with an existing output schema and annotations covering the safety profile, the description covers everything needed to invoke it correctly: purpose, when to call, prerequisite, next steps, and the key caveat about snapshot lag. Nothing critical is missing for an agent to select and call this tool.

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 the baseline is 3. The description does not add parameter-level semantics beyond what the schema already provides; it references symbol via examples (BTC, AAPL) but doesn't clarify parameter behavior or constraints beyond the schema's own descriptions of market_id, symbol, and coin. The schema fully handles the parameter documentation.

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 clearly states a specific purpose: 'Role-aware signal alignment per symbol (timing / trend / swing / regime) plus hierarchy alignment.' This names the resource (per-symbol, multi-timeframe) and the action (alignment check), distinguishing it from siblings like get_signal_detail or get_cross_market_correlation. The trigger examples reinforce the specific use case.

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?

It provides an explicit 'When to call: multi-timeframe analysis, cross-role agreement checks' plus concrete trigger examples, including casual phrasings. It also notes a prerequisite (get_signal_detail recommended) and next steps. However, it does not explicitly mention when NOT to use it or name alternative tools for comparison, so it falls just short of a 5.

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.