OneQAZ Trading Intelligence

Symbol Peer Links

get_symbol_peer_links_tool

Read-onlyIdempotent

Purpose: Symbol-level lead-lag links (e.g. META -> AMZN, lag=15m, rho=+0.53). When symbol is set, only peers that lead or follow that symbol are returned. Triggers (casual questions too): "what moves before NVDA?", "이 종목보다 먼저 움직이는 종목 있어?", "which stocks follow AAPL?", "선행 종목 알려줘", "any early-warning peers for this ticker?". When to call: incorporate peer leading signals into single-symbol reasoning. Prerequisites: none. Next steps: get_signal_detail for the peer's signal context. Caveats: 14-day lookback, 15-minute bars.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`top_k`	No	Number of top links to return
`symbol`	No	Optional. When set, peers are anchored to this symbol.
`market_id`	No	coin / kr_stock / us_stock. Aliases coin/kr/us and any letter case are accepted.	us_stock

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_symbol_peer_links_tool — 실응답에서 추출(2026-09-23).",
+        "properties": {
+          "as_follow": {
+            "items": {},
+            "type": "array"
+          },
+          "as_lead": {
+            "items": {},
+            "type": "array"
+          },
+          "focus_symbol": {
+            "anyOf": [
+              {},
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "market_id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "total_links": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "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 / market_id / description

Added value: +"coin / 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: +"Optional. When set, peers are anchored to this symbol."

addedInput schema / properties / top_k / description
```
Added value: +"Number of top links to return"
```

AddedMay 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent, so the safety profile is covered. The description adds real behavioral context beyond that: a 14-day lookback window and 15-minute bar granularity, which materially affect interpretation of results. It does not mention rate limits or latency, keeping it short of a 5.

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) are front-loaded and skimmable, with the core purpose in the first line. The multiline, tri-lingual trigger list is functional but somewhat verbose, so it is efficient without being maximally tight.

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?

With an output schema present, return values need not be explained, and the description still covers scope, triggers, prerequisites, follow-up tool, and data caveats. Nothing an agent needs to select or invoke the tool correctly is missing.

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 documents top_k, symbol, and market_id (including enum aliases). The description only restates the anchoring behavior of `symbol` and says nothing new about top_k or market_id, so it sits at the baseline rather than adding value.

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?

States a specific verb+resource ('Symbol-level lead-lag links') and concretizes it with an example ('META -> AMZN, lag=15m, rho=+0.53'), so the agent knows exactly what shape of data comes back. It distinguishes the anchored mode ('only peers that lead or follow that symbol') and points to a distinct next-step sibling, making it separable from get_cross_market_correlation and get_signal_detail.

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?

Provides explicit triggers including casual/multilingual phrasings ('what moves before NVDA?', '선행 종목 알려줘'), a when-to-call condition (incorporate peer leading signals into single-symbol reasoning), prerequisites (none), and a next step. This is about as complete as usage guidance gets.

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.