OneQAZ Trading Intelligence

get_signal_detail

Read-onlyIdempotent

Purpose: Per-symbol signal deep-dive — latest signal + history + feedback. Triggers (casual questions too): "why is BTC a buy?", "그 시그널 근거가 뭐야?", "signal history for AAPL?", "이 종목 시그널 자세히 보여줘", "how has this signal performed before?". When to call: drilling into a single ticker's signal context. Prerequisites: confirm existence via get_signals first. Next steps: get_role_analysis, get_position_detail. Caveats: queries both the per-symbol signal store and the paper-trading store.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`coin`	No	Legacy alias of symbol (kept for backward compatibility)
`symbol`	No	Asset identifier (preferred; e.g., BTC, AAPL)
`interval`	No	Timeframe (default: combined)	combined
`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_signal_detail — 실응답에서 추출(2026-09-23).",
+        "properties": {
+          "interval": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "latest_signal": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "market_id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "pattern_feedback": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "recent_history": {
+            "items": {},
+            "type": "array"
+          },
+          "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"
+]

Changed6 schema fields changedSep 22, 2026

addedInput schema / properties / coin / description

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

addedInput schema / properties / interval / description
```
Added value: +"Timeframe (default: combined)"
```

addedInput schema / properties / interval / enum

Added value: +[
+  "5m",
+  "15m",
+  "30m",
+  "240m",
+  "1d",
+  "combined"
+]

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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description doesn't need to repeat safety. It adds value by disclosing that the tool queries two stores ('per-symbol signal store and paper-trading store'), which is useful for understanding scope. A slight deduction for not explaining what happens if symbol doesn't exist, but overall strong.

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?

The description is well-structured with clear sections: Purpose, Triggers, When to call, Prerequisites, Next steps, Caveats. It is front-loaded with purpose and examples, and every sentence adds value. No fluff.

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?

Given the tool's complexity (4 params, one required) and the presence of an output schema, the description covers essentials: purpose, usage, prerequisites. It could mention error handling or specific output contents, but the output schema likely covers that. Minor gap: it doesn't explain why the symbol must be confirmed via get_signals, but otherwise complete.

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 schema already explains each parameter well. The description adds context for symbol (likely the core parameter) and mentions the default interval 'combined' implicitly. But it doesn't add much beyond the schema, so baseline 3 is appropriate.

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 the tool's purpose: 'Per-symbol signal deep-dive — latest signal + history + feedback.' It uses a specific verb ('get') and resource ('signal detail') and distinguishes itself from siblings like get_signals. The triggers and examples (e.g., 'why is BTC a buy?') make it unmistakable.

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 states 'When to call' and provides prerequisites ('confirm existence via get_signals first'). It also suggests next steps and names alternatives implicitly through the prerequisite. This is clear, actionable guidance.

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.