Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

Screener User Strategies

screener_user_strategies
Read-onlyIdempotent

List your saved screener strategies by market (US, HK, CN, SG). Use returned IDs to run via screener_search or inspect conditions via 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
NameRequiredDescriptionDefault
marketNoMarket filter: "US" | "HK" | "CN" | "SG" (default: "US")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
strategysNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.8.7
    • addedOutput schema / $defs / ScreenerStrategyItem / properties / description
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"ScreenerUserStrategiesParam"
  3. Changed11 schema fields changedv0.6.0
    • 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"
  4. Changed1 schema field changedv0.5.6
    • 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"
+}
  5. Addedv0.4.5

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the market parameter scope but does not provide additional behavioral context such as return formats or error behavior. Since annotations are strong, the bar is lower, and the description adds minimal extra value, so a 3 is appropriate.

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 concise, consisting of two sentences. The first sentence states the core purpose, and the second provides usage guidance and cross-references. It is front-loaded and has zero waste, making it easy to scan.

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?

For a simple read-only list tool with one optional parameter, the description is complete. The output schema is present (as per context signals), so return value details are covered. The description provides enough context for the agent to know when and how to invoke it, including the market filter and downstream use of the id.

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 schema covers the single parameter 'market' with 100% description coverage, including allowed values and default. The description repeats this information ("market: US|HK|CN|SG (default: US)") without adding any new semantic meaning, such as format, examples, or interplay with other parameters. Since schema does the heavy lifting, the baseline of 3 applies.

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 clearly states the purpose: "List the current user's saved screener strategies." It specifies the resource (user's saved screener strategies) and the operation (list). It also distinguishes from sibling tools like screener_recommend_strategies (recommended vs. user's own) and screener_strategy (inspect conditions vs. list).

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 provides clear context on when to use the tool: to list the user's saved strategies. It also gives guidance on the workflow: "Pass id to screener_search strategy_id to run, or screener_strategy to inspect conditions." This implies downstream usage, but it does not explicitly state when NOT to use it or contrast with alternatives for listing, so it falls slightly short of a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/longbridge/longbridge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server