OneQAZ Trading Intelligence

Profitable Positions

get_profitable_positions

Read-onlyIdempotent

Purpose: Profitable paper positions (ROI > 0). Convenience wrapper around get_positions(min_roi=0.01). Triggers (casual questions too): "what's winning right now?", "지금 뭐가 수익 나고 있어?", "show me the green ones", "best open positions?", "어떤 종목이 잘 가고 있어?". When to call: quickly surface winning tickers. Prerequisites: none. Next steps: get_position_detail for full context. Caveats: paper-trading data only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max results (default 20)
`market_id`	Yes	Market ID (crypto, kr_stock, us_stock; aliases coin/kr/us accepted)

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_profitable_positions — 실응답에서 추출(2026-09-23).",
+        "properties": {
+          "common": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "common_note": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "filters": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "limit": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "market_id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "positions": {
+            "items": {},
+            "type": "array"
+          },
+          "returned": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "stats": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "stats_scope": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null
+          },
+          "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"
+]

Changed3 schema fields changedSep 22, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Max results (default 20)"
```
- addedInput schema / properties / market_id / description
```
Added value: +"Market ID (crypto, kr_stock, us_stock; aliases coin/kr/us accepted)"
```
- addedInput schema / properties / market_id / enum
```
Added value: +[
+  "crypto",
+  "kr_stock",
+  "us_stock"
+]
```
First observedApr 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds real context beyond that: the ROI > 0 threshold semantics, the wrapper relationship to get_positions, and the 'paper-trading data only' caveat. It stops short of describing return shape or pagination, which keeps it from 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?

It is labeled and front-loaded (Purpose, Triggers, When to call, Prerequisites, Next steps, Caveats), which makes it scannable. However, the bilingual casual-trigger list is longer than needed; a couple of examples would carry the same meaning with less bulk.

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 and annotations covering the safety/read profile, the description supplies everything else an agent needs: what counts as profitable, that it is paper-only, that it wraps get_positions, and where to go for detail. Nothing material 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 both parameters (market_id enum, limit) are fully documented in the schema, so the baseline is 3. The description only gestures at parameterization through the min_roi=0.01 reference and adds no syntax beyond the schema.

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 ('Profitable paper positions') and pins the scope precisely with 'ROI > 0'. It also distinguishes itself from the sibling get_positions by defining itself as a 'Convenience wrapper around get_positions(min_roi=0.01)', so an agent can tell the two apart without opening schemas.

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 gives explicit 'When to call' guidance ('quickly surface winning tickers'), samples of casual triggers, a 'Prerequisites: none' note, and a 'Next steps' pointer to get_position_detail. The alternative (get_positions with min_roi) is named, so both the when and the routing are covered.

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.