Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Screener Strategy

screener_strategy
Read-onlyIdempotent

Check a screener strategy's filter conditions before running it. Provide the strategy ID to review its criteria, then execute via screener_search.

Instructions

Inspect a screener strategy's filter conditions before running it. Use screener_search strategy_id to execute the strategy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesStrategy ID from screener_recommend_strategies or screener_user_strategies screeners[].id
_jqNoOptional 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • 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."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "ScreenerStrategyFilter": {
-      "properties": {
-        "key": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "max": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "min": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "tech_values": {}
-      },
-      "type": "object"
-    },
-    "ScreenerStrategyFilterGroup": {
-      "properties": {
-        "filters": {
-          "items": {
-            "$ref": "#/$defs/ScreenerStrategyFilter"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "filter": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/ScreenerStrategyFilterGroup"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "market": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"ScreenerStrategyParam"
  4. Changed12 schema fields changedv0.6.0
    • removedOutput schema / $defs / ScreenerStrategyFilter / description
      Removed value: -"A single filter condition within a screener strategy. The `filter_` prefix\nis stripped from `key` by the tool so it matches `screener_indicators` and\n`screener_search` condition input."
    • removedOutput schema / $defs / ScreenerStrategyFilter / properties / key / description
      Removed value: -"Indicator key (without the `filter_` prefix)."
    • removedOutput schema / $defs / ScreenerStrategyFilter / properties / max / description
      Removed value: -"Upper bound for the condition (string, may be empty)."
    • removedOutput schema / $defs / ScreenerStrategyFilter / properties / min / description
      Removed value: -"Lower bound for the condition (string, may be empty)."
    • removedOutput schema / $defs / ScreenerStrategyFilter / properties / tech_values / description
      Removed value: -"Technical-indicator value selection for technical keys. Passthrough\nobject whose shape depends on the indicator (see `screener_indicators`)."
    • removedOutput schema / $defs / ScreenerStrategyFilterGroup / description
      Removed value: -"The `filter` wrapper of a screener strategy, holding the condition list."
    • removedOutput schema / $defs / ScreenerStrategyFilterGroup / properties / filters / description
      Removed value: -"Filter conditions making up the strategy."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `screener_strategy`. Documented portion is `market` plus the\n`filter.filters[]` condition list."
    • removedOutput schema / properties / filter / description
      Removed value: -"Filter group containing the strategy's conditions."
    • removedOutput schema / properties / market / description
      Removed value: -"Market the strategy targets, e.g. \"US\" / \"HK\" / \"CN\" / \"SG\"."
    • removedOutput schema / title
      Removed value: -"ScreenerStrategyResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "ScreenerStrategyFilter": {
+      "description": "A single filter condition within a screener strategy. The `filter_` prefix\nis stripped from `key` by the tool so it matches `screener_indicators` and\n`screener_search` condition input.",
+      "properties": {
+        "key": {
+          "description": "Indicator key (without the `filter_` prefix).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "max": {
+          "description": "Upper bound for the condition (string, may be empty).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "min": {
+          "description": "Lower bound for the condition (string, may be empty).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "tech_values": {
+          "description": "Technical-indicator value selection for technical keys. Passthrough\nobject whose shape depends on the indicator (see `screener_indicators`)."
+        }
+      },
+      "type": "object"
+    },
+    "ScreenerStrategyFilterGroup": {
+      "description": "The `filter` wrapper of a screener strategy, holding the condition list.",
+      "properties": {
+        "filters": {
+          "description": "Filter conditions making up the strategy.",
+          "items": {
+            "$ref": "#/$defs/ScreenerStrategyFilter"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `screener_strategy`. Documented portion is `market` plus the\n`filter.filters[]` condition list.",
+  "properties": {
+    "filter": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/ScreenerStrategyFilterGroup"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Filter group containing the strategy's conditions."
+    },
+    "market": {
+      "description": "Market the strategy targets, e.g. \"US\" / \"HK\" / \"CN\" / \"SG\".",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "title": "ScreenerStrategyResponse",
+  "type": "object"
+}
  6. Addedv0.4.5

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the 'before running it' context, which is useful, but does not disclose anything else about behavior, such as what happens with invalid IDs or the response structure. Given the strong annotations, 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?

Two sentences with zero waste: the first states the purpose, the second gives the execution alternative. The purpose is front-loaded and every word earns its place.

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 tool with one required parameter and no output schema, the description is complete. It explains what the tool does, how to obtain the ID, and how to proceed if execution is needed. Nothing essential is missing for an agent to call it correctly.

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 the schema already explains both parameters well, including where to get the id from. The description itself does not add parameter details beyond pointing to screener_search, which is not necessary. Baseline 3 is correct when the schema carries the burden.

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 verb 'Inspect' and the resource 'a screener strategy's filter conditions', distinguishing it from execution. It explicitly names screener_search as the execution alternative, so an agent can tell them 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 says to inspect before running and directs the agent to use screener_search strategy_id to execute. This explicitly provides when-to-use and points to the alternative tool, leaving no ambiguity.

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

Deploy Server

Other Tools