OneQAZ Trading Intelligence

Group Context

get_group_context

Read-onlyIdempotent

Use when the question is about a sector, theme, ETF basket or index basket — its structure state and its members. Returns headline claims, the group's regime state per interval, its market, groups that co-move with it, member symbols with their latest signal bias, symbols the basket leads, and gaps. Not for a single stock (use get_symbol_context) or a whole market (use get_market_context). Provides regime, signal-score and linkage context with sample sizes and measured hit rates; every link carries its evidence and every empty section is listed in gaps. Not a real-time quote, fundamentals, or full-text news source.

Input Schema

TableJSON Schema

Name	Required	Description
`group`	Yes	OneQAZ structure group id (kr_semiconductor, technology, broad_index), a sector word (반도체, energy) or an ETF ticker that belongs to a group (QQQ).
`limit`	No	Max links per section (default 8, max 50; members default 10).
`question`	No	Optional. The user's original question, used only for service improvement analytics. Does not change the response.
`market_id`	No	Optional. crypto / kr_stock / us_stock (aliases coin/kr/us). Group ids repeat across markets.

Output Schema

TableJSON Schema

Name	Required	Description
`gaps`	No
`meta`	No
`news`	No
`self`	No
`peers`	No
`entity`	No
`headline`	No
`upstream`	No
`timestamp`	Yes	RFC3339 UTC, server build time
`disclaimer`	Yes	Canonical compliance disclaimer (always present)
`downstream`	No
`request_id`	Yes	32-hex per-response correlation id
`resolution`	No
`data_classification`	No
`is_investment_advice`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

addedInput schema / properties / question

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional. The user's original question, used only for service improvement analytics. Does not change the response."
+}

AddedOct 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only provide the read-only/idempotent safety profile; the description goes well beyond them by enumerating the content sections returned (headline claims, regime per interval, co-moving groups, members with signal bias, leads, gaps), noting that links carry evidence and sample sizes and hit rates, that empty sections are listed in gaps, and that it is not a quote/fundamentals/news source. This is rich behavioral disclosure that annotations cannot convey.

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?

Four short sentences, front-loaded with the selection condition, then the payload, then the exclusions, then the quality caveats. The enumerations are dense but each clause adds distinct routing or expectation-setting information with no filler.

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?

An output schema exists, yet the description still makes the shape of the answer predictable and covers negative scope (no real-time quotes, fundamentals, or full-text news) plus evidence-quality caveats. Nothing an agent needs in order to call or trust this tool 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% and the schema already documents the group id format, the limit default/max, the market_id enum, and that question is analytics-only. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

'Use when the question is about a sector, theme, ETF basket or index basket — its structure state and its members' states a specific resource and scope, and it explicitly names the sibling tools it is NOT for (get_symbol_context, get_market_context). An agent can route to it without opening any schema.

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?

Gives an explicit trigger condition (sector/theme/ETF/index basket questions), names both excluded cases (single stock, whole market) and names the alternative tool for each. Nothing about when to select this tool is left to inference.

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.