longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Screener User Strategies

screener_user_strategies

Read-onlyIdempotent

Retrieve your saved screener strategies for US, HK, CN, or SG markets, then run or inspect their conditions via screener_search or screener_strategy.

Instructions

List the current user's saved screener strategies. market: US|HK|CN|SG (default: US). Pass id to screener_search strategy_id to run, or screener_strategy to inspect conditions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`_jq`	No	Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data \| map({symbol}). Omit for the full response.
`market`	No	Market filter: "US" \| "HK" \| "CN" \| "SG" (default: "US")

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.12.0Sep 23, 2026

addedInput schema / properties / _jq / description

Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."

Changed2 schema fields changedv0.10.6Sep 10, 2026

addedInput schema / properties / _jq
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "ScreenerStrategyItem": {
-      "properties": {
-        "description": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "market": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "risk": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "three_months_chg": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "strategys": {
-      "items": {
-        "$ref": "#/$defs/ScreenerStrategyItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.8.7Aug 19, 2026
- addedOutput schema / $defs / ScreenerStrategyItem / properties / description
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"ScreenerUserStrategiesParam"
```

Changed11 schema fields changedv0.6.0Jun 26, 2026

removedOutput schema / $defs / ScreenerStrategyItem / description

Removed value: -"A single screener strategy entry. Subset of upstream fields; the change\nfigure is stringified by the transform pipeline."

removedOutput schema / $defs / ScreenerStrategyItem / properties / description

Removed value: -{
-  "description": "Strategy description.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / $defs / ScreenerStrategyItem / properties / id / description

Removed value: -"Strategy ID. Pass to `screener_search` `strategy_id` to run, or to\n`screener_strategy` to inspect the filter conditions."

removedOutput schema / $defs / ScreenerStrategyItem / properties / market / description

Removed value: -"Market the strategy targets, e.g. \"US\" / \"HK\" / \"CN\" / \"SG\"."

removedOutput schema / $defs / ScreenerStrategyItem / properties / name / description
```
Removed value: -"Strategy display name."
```
removedOutput schema / $defs / ScreenerStrategyItem / properties / risk / description
```
Removed value: -"Risk classification label."
```
removedOutput schema / $defs / ScreenerStrategyItem / properties / three_months_chg / description
```
Removed value: -"Trailing three-month change (stringified decimal / percentage)."
```

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / description

Removed value: -"Returned by `screener_recommend_strategies` and `screener_user_strategies`.\nThe documented portion is `strategys[]`."

removedOutput schema / properties / strategys / description

Removed value: -"Screener strategies (note the upstream `strategys` spelling)."

removedOutput schema / title

Removed value: -"ScreenerStrategiesResponse"

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ScreenerStrategyItem": {
+      "description": "A single screener strategy entry. Subset of upstream fields; the change\nfigure is stringified by the transform pipeline.",
+      "properties": {
+        "description": {
+          "description": "Strategy description.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "Strategy ID. Pass to `screener_search` `strategy_id` to run, or to\n`screener_strategy` to inspect the filter conditions.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "market": {
+          "description": "Market the strategy targets, e.g. \"US\" / \"HK\" / \"CN\" / \"SG\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Strategy display name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "risk": {
+          "description": "Risk classification label.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "three_months_chg": {
+          "description": "Trailing three-month change (stringified decimal / percentage).",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `screener_recommend_strategies` and `screener_user_strategies`.\nThe documented portion is `strategys[]`.",
+  "properties": {
+    "strategys": {
+      "description": "Screener strategies (note the upstream `strategys` spelling).",
+      "items": {
+        "$ref": "#/$defs/ScreenerStrategyItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "ScreenerStrategiesResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, so the description doesn't need to repeat that. It adds that the results are scoped to the current user and that market defaults to US, which is useful context. No extra disclosure about pagination or response shape is given, but the bar is lower given the 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?

Two sentences with zero filler: the first states the core purpose, the second explains the market parameter and how to chain the output into sibling tools. Every sentence earns its place and the important information is front-loaded.

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 simple read-only list tool with two optional parameters and no output schema, the description covers the essential points: what it returns, the market filter, and how the result feeds into other tools. A mention of the output structure or pagination would be nice, but it's not critical here given the tool's simplicity.

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 the parameters are fully documented in the schema. The description repeats the market enum and default, adding no new meaning beyond what the schema already says. It doesn't explain _jq, but the schema does, so baseline 3 is appropriate.

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 'List the current user's saved screener strategies', a specific verb and resource that clearly distinguishes this from sibling tools like screener_recommend_strategies, screener_search, and screener_strategy. It also names those siblings and explains how they relate.

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?

It gives practical context by telling the agent what to do with the returned id: pass to screener_search to run, or to screener_strategy to inspect conditions. It doesn't explicitly say when *not* to use this tool or compare it with other list-like tools, but the usage guidance is concrete and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Screener User Strategies

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools