Skip to main content
Glama

OneQAZ Trading Intelligence

by io.github.wnsod
OverviewDiscussionsAdmin

get_trade_outcomes_bulk

Read-onlyIdempotent

Purpose: Cursor-paginated bulk export of the prediction -> trade -> outcome chain — paper trades with realized P&L, each linked (best-effort, same-symbol 2h window) to the signal prediction that preceded entry. Built for pipeline consumers who need offline backtesting data, not conversational snippets. Triggers: "give me your full trade history for backtesting", "bulk export trades", "예측이 실제 매매 성과로 이어졌는지 원데이터로 검증하고 싶다", "download outcomes". When to call: offline verification, periodic ingestion into a research pipeline, or auditing whether signals translate into realized outcomes. Prerequisites: none. For the prediction ledger itself use get_resolved_predictions. Next steps: follow next_cursor until has_more=false; get_resolved_predictions to cross-check linked predictions against the tamper-evident ledger. Caveats: linkage is temporal matching, NOT a foreign key (see meta.linkage). Paper trading only — envelope carries the standard disclaimer once per page. Output: full_data { market, trades[] {id, symbol, action, entry/exit price+ts, profit_loss_pct, holding_duration, entry_signal_score, regime fields, policy_version, sizing fields, linked_prediction{...}|null}, count, linked_prediction_count, next_cursor, has_more, meta }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoexit-time window in days (max 120)
limitNoPage size (default 50, max 500). Cursor-paginated: follow next_cursor while has_more is true to retrieve everything.
cursorNolast trade id from previous page (0 = start)
marketNo"crypto" (default) / "kr_stock" / "us_stock"crypto

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
full_dataNo
timestampYesRFC3339 UTC, server build time
disclaimerYesCanonical compliance disclaimer (always present)
request_idYes32-hex per-response correlation id
is_real_moneyNo
data_classificationNo
is_investment_adviceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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_trade_outcomes_bulk — 실응답에서 추출(2026-09-23).",
+        "properties": {
+          "count": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "has_more": {
+            "anyOf": [
+              {
+                "type": "boolean"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "linked_prediction_count": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "market": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "meta": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "next_cursor": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "trades": {
+            "items": {},
+            "type": "array"
+          },
+          "window_days": {
+            "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"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / default
      Previous value: -200New value: +50
    • changedInput schema / properties / limit / description
      Previous value: -"page size (max 500)"New value: +"Page size (default 50, max 500). Cursor-paginated: follow next_cursor while has_more is true to retrieve everything."
  3. Changed4 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"last trade id from previous page (0 = start)"
    • addedInput schema / properties / days / description
      Added value: +"exit-time window in days (max 120)"
    • addedInput schema / properties / limit / description
      Added value: +"page size (max 500)"
    • addedInput schema / properties / market / description
      Added value: +"\"crypto\" (default) / \"kr_stock\" / \"us_stock\""
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, establishing safety. The description adds crucial behavioral context beyond annotations: linkage is temporal matching not a foreign key (with a pointer to meta.linkage), paper trading only, per-page disclaimer, and the pagination contract (follow next_cursor until has_more=false). No contradiction with annotations.

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 structured with labeled sections (Purpose, Triggers, When to call, Prerequisites, Next steps, Caveats, Output) that front-load the most important information and organize details efficiently. Every section adds value; there is no filler or redundancy. The use of section headers makes it scannable for an agent.

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?

The description is unusually complete for a bulk-export tool: it covers purpose, triggers, usage context, prerequisites, next steps, caveats, and even a full output structure. With an output schema present, return-value documentation is optional, but the description still provides it. An agent has everything needed to invoke the tool correctly and interpret results.

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?

The input schema provides 100% coverage with detailed descriptions for each parameter (days, limit, cursor, market). The tool description does not add additional semantics about these parameters beyond what the schema already offers; the schema itself explains defaults, bounds, and the cursor's role. Baseline 3 is appropriate given the schema's completeness.

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 opens with a precise purpose: 'Cursor-paginated bulk export of the prediction -> trade -> outcome chain.' It specifies what the tool returns (paper trades with realized P&L, linked to signal predictions) and explicitly names the sibling it is not ('For the prediction ledger itself use get_resolved_predictions'). This is a specific verb+resource with clear differentiation from siblings like get_trade_history and get_resolved_predictions.

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?

The description includes an explicit 'When to call' section listing concrete scenarios (offline verification, periodic ingestion, auditing signal-to-outcome translation). It also states 'Prerequisites: none' and routes the user to get_resolved_predictions for the prediction ledger, directly addressing when not to use this tool. This is exemplary usage 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 toolsInspect
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.

Resources