OneQAZ Trading Intelligence

get_feature_governance_state

Read-onlyIdempotent

Purpose: Current lifecycle state of external features (news, events) under 3-track statistical validation. Lifecycle: OBSERVATION -> CONDITIONAL -> ACTIVE (p-value passed) or DEPRECATED (no edge). Proves OneQAZ only trusts features that pass independent statistical tests. Triggers (casual questions too): "do you validate your own inputs?", "피처 검증은 어떻게 해?", "which signals passed testing?", "통계 검증 통과한 피처 뭐야?", "how do you avoid junk features?". When to call: meta-level trust audit ("do they validate their own inputs?"). Prerequisites: none. Next steps: none (meta evidence). Caveats: empty when feature_gate_evaluator has not yet run cycles. Rows are paginated — read total_available (not len(features)) for the whole-set size. status_summary, meta.* and interpretation are always computed over the whole set, never over the returned page.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 50, max 500). Rows are truncated; see `total_available` and `truncated` in the response. `status_summary` and `meta` counts stay whole-set.
`market_id`	No	Optional market filter (defaults to coin). Aliases coin/kr/us and any letter case are accepted.
`status_filter`	No	Optional status filter (OBSERVATION, CONDITIONAL, ACTIVE, DEPRECATED)
`target_market`	No	Alias for market_id (backward compat)

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_feature_governance_state — 실응답에서 추출(2026-09-23).",
+        "properties": {
+          "common": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "common_note": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "features": {
+            "items": {},
+            "type": "array"
+          },
+          "limit": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "meta": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "returned": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "status_summary": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "total_available": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "truncated": {
+            "anyOf": [
+              {
+                "type": "boolean"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "truncated_note": {
+            "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"
+]

Changed12 schema fields changedSep 22, 2026

addedInput schema / properties / market_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / market_id / description

Added value: +"Optional market filter (defaults to coin). Aliases coin/kr/us and any letter case are accepted."

addedInput schema / properties / market_id / enum

Added value: +[
+  "crypto",
+  "kr_stock",
+  "us_stock"
+]

removedInput schema / properties / market_id / type
```
Removed value: -"string"
```

addedInput schema / properties / status_filter / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / status_filter / description

Added value: +"Optional status filter (OBSERVATION, CONDITIONAL, ACTIVE, DEPRECATED)"

addedInput schema / properties / status_filter / enum

Added value: +[
+  "OBSERVATION",
+  "CONDITIONAL",
+  "ACTIVE",
+  "DEPRECATED"
+]

removedInput schema / properties / status_filter / type
```
Removed value: -"string"
```

addedInput schema / properties / target_market / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / target_market / description
```
Added value: +"Alias for market_id (backward compat)"
```

addedInput schema / properties / target_market / enum

Added value: +[
+  "crypto",
+  "kr_stock",
+  "us_stock"
+]

removedInput schema / properties / target_market / type
```
Removed value: -"string"
```

Changed1 schema field changedSep 22, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 50,
+  "description": "Max results (default 50, max 500). Rows are truncated; see `total_available` and `truncated` in the response. `status_summary` and `meta` counts stay whole-set.",
+  "type": "integer"
+}

First observedApr 19, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond annotations declaring readOnly/openWorld/idempotent, the description discloses important pagination behavior: rows are paginated, `total_available` must be used instead of `len(features)`, and aggregate fields are computed over the whole set rather than the returned page. It also notes the empty-result caveat when the feature gate evaluator has not run.

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 uses clear labeled sections (Purpose, Triggers, When to call, Prerequisites, Caveats) and front-loads the essential purpose. Every sentence carries operational value, including the pagination caveat and trigger examples.

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?

Given the output schema exists and annotations are already available, the description adds the missing behavioral and contextual pieces: lifecycle semantics, trigger examples, pagination caveats, and the case where the result may be empty. An agent has enough information to call it correctly without further guesswork.

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 nuance beyond what the schema already documents, but it does not need to; the schema handles parameter semantics and the description covers response caveats.

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 names a specific resource ('current lifecycle state of external features') and a precise domain ('3-track statistical validation'), then defines the lifecycle stages. It also distinguishes itself from a trust-audit perspective with 'Proves OneQAZ only trusts features that pass independent statistical tests.'

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?

The description gives explicit 'When to call' guidance ('meta-level trust audit') and lists concrete trigger phrases, including casual non-technical questions. It does not name an alternative tool or state when not to call, but the provided context is strong enough for an agent to route correctly.

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.