OneQAZ Trading Intelligence

Market Context

get_market_context

Read-onlyIdempotent

Use when the question is about a whole market (KR, US, CRYPTO) — its structure regime and how its groups are positioned. Returns headline claims, the market's structure and global macro regime, the macro categories assumed to affect it (with tuned lags), its groups ordered by distance from the middle regime stage, market-tagged news, and gaps. Not for one sector or stock (use get_group_context or get_symbol_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
`limit`	No	Max links per section (default 8, max 50).
`market`	Yes	crypto / kr_stock / us_stock, or a market word (KR, 국장, 코스피, US, 미장, 나스닥, 코인).
`question`	No	Optional. The user's original question, used only for service improvement analytics. Does not change the response.

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

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds behavioral context beyond that: it reports sample sizes and measured hit rates, states that every link carries its evidence, and that every empty section appears in gaps. That is meaningful non-obvious behavior disclosure, though it does not discuss auth, limits, or freshness.

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?

It is front-loaded with a single usage sentence followed by a payload inventory, with essentially no filler. The payload enumeration is dense and long, but each clause adds information rather than repeating the name, so it remains efficient.

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?

For a read-only market context tool with an output schema covering return structure, the description supplies the usage routing, payload overview, evidence/confidence disclosure, and gaps behavior that an agent needs to select it correctly. It does not cover pagination interaction with the limit parameter or freshness, minor gaps given a read-only, idempotent tool with an output schema.

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 coverage is 100%, so all three parameters are documented in the schema itself, including the market word list and the limit default/max. The description adds the market group naming (KR, US, CRYPTO) but no syntax or format detail beyond the schema, so it sits at the baseline.

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 states a specific verb-resource pair ('whole market ... structure regime and how its groups are positioned') and explicitly names the sibling alternatives it is not (get_group_context, get_symbol_context). It also enumerates the concrete return payload (headline claims, structure and macro regime, tuned lags, groups ordered by distance, news, gaps), leaving no ambiguity about what the tool produces.

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?

It specifies when to use it ('when the question is about a whole market (KR, US, CRYPTO)') and when not to ('Not for one sector or stock — use get_group_context or get_symbol_context'), and it further rules out real-time quotes, fundamentals, and full-text news as sources. Both sides of the routing decision are given explicitly with named alternatives.

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.