longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Screener Indicators

screener_indicators

Read-onlyIdempotent

Retrieve available screener indicators with units, ranges, and technical indicator options to filter stocks by categories and periods.

Instructions

Get all available screener indicator keys with units and default value ranges. Technical indicators include a tech_values field showing available options (e.g. macd_day: {category:[goldenfork,deadcross], period:[day,week]}).

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.
`symbol`	No	Optional security symbol to filter indicators for a specific stock, e.g. "AAPL.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": {
-    "ScreenerIndicator": {
-      "properties": {
-        "default_range": {
-          "anyOf": [
-            {
-              "$ref": "#/$defs/ScreenerIndicatorRange"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "key": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "tech_values": {},
-        "unit": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "ScreenerIndicatorGroup": {
-      "properties": {
-        "group_name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "indicators": {
-          "items": {
-            "$ref": "#/$defs/ScreenerIndicator"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "ScreenerIndicatorRange": {
-      "properties": {
-        "max": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "min": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "groups": {
-      "items": {
-        "$ref": "#/$defs/ScreenerIndicatorGroup"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"ScreenerIndicatorsParam"
```

Changed17 schema fields changedv0.6.0Jun 26, 2026

removedOutput schema / $defs / ScreenerIndicator / description

Removed value: -"A single screener indicator's metadata. The `filter_` prefix is stripped\nfrom `key` by the tool. `tech_values`, when present, is a synthesized schema\n(`{tech_key: [{value, label}, ...]}`) describing the options a technical\nindicator accepts."

removedOutput schema / $defs / ScreenerIndicator / properties / default_range / description
```
Removed value: -"Default value range for the indicator."
```
removedOutput schema / $defs / ScreenerIndicator / properties / id / description
```
Removed value: -"Indicator ID."
```
removedOutput schema / $defs / ScreenerIndicator / properties / key / description
```
Removed value: -"Indicator key (without the `filter_` prefix)."
```
removedOutput schema / $defs / ScreenerIndicator / properties / name / description
```
Removed value: -"Indicator display name."
```

removedOutput schema / $defs / ScreenerIndicator / properties / tech_values / description

Removed value: -"For technical indicators: synthesized schema of accepted option values,\nkeyed by technical sub-key, each mapping to a list of `{value, label}`."

removedOutput schema / $defs / ScreenerIndicator / properties / unit / description
```
Removed value: -"Value unit, where applicable."
```
removedOutput schema / $defs / ScreenerIndicatorGroup / description
```
Removed value: -"A named group of screener indicators."
```
removedOutput schema / $defs / ScreenerIndicatorGroup / properties / group_name / description
```
Removed value: -"Group display name."
```
removedOutput schema / $defs / ScreenerIndicatorGroup / properties / indicators / description
```
Removed value: -"Indicators in this group."
```
removedOutput schema / $defs / ScreenerIndicatorRange / description
```
Removed value: -"Default value range for a screener indicator."
```
removedOutput schema / $defs / ScreenerIndicatorRange / properties / max / description
```
Removed value: -"Default upper bound (string)."
```
removedOutput schema / $defs / ScreenerIndicatorRange / properties / min / description
```
Removed value: -"Default lower bound (string)."
```

removedOutput schema / $schema

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

removedOutput schema / description

Removed value: -"Returned by `screener_indicators`. Documented portion is `groups[]`."

removedOutput schema / properties / groups / description

Removed value: -"Indicator metadata grouped by category."

removedOutput schema / title

Removed value: -"ScreenerIndicatorsResponse"

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ScreenerIndicator": {
+      "description": "A single screener indicator's metadata. The `filter_` prefix is stripped\nfrom `key` by the tool. `tech_values`, when present, is a synthesized schema\n(`{tech_key: [{value, label}, ...]}`) describing the options a technical\nindicator accepts.",
+      "properties": {
+        "default_range": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/ScreenerIndicatorRange"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Default value range for the indicator."
+        },
+        "id": {
+          "description": "Indicator ID.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "key": {
+          "description": "Indicator key (without the `filter_` prefix).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Indicator display name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "tech_values": {
+          "description": "For technical indicators: synthesized schema of accepted option values,\nkeyed by technical sub-key, each mapping to a list of `{value, label}`."
+        },
+        "unit": {
+          "description": "Value unit, where applicable.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "ScreenerIndicatorGroup": {
+      "description": "A named group of screener indicators.",
+      "properties": {
+        "group_name": {
+          "description": "Group display name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "indicators": {
+          "description": "Indicators in this group.",
+          "items": {
+            "$ref": "#/$defs/ScreenerIndicator"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "ScreenerIndicatorRange": {
+      "description": "Default value range for a screener indicator.",
+      "properties": {
+        "max": {
+          "description": "Default upper bound (string).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "min": {
+          "description": "Default lower bound (string).",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `screener_indicators`. Documented portion is `groups[]`.",
+  "properties": {
+    "groups": {
+      "description": "Indicator metadata grouped by category.",
+      "items": {
+        "$ref": "#/$defs/ScreenerIndicatorGroup"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "ScreenerIndicatorsResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already cover the safety profile: readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds a scope guarantee ('all available') and response details, but it does not disclose additional behavioral constraints such as pagination, rate limits, or auth expectations. There is 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 two compact, front-loaded sentences. The first states the core purpose, and the second adds a concrete example of the tech_values structure. 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 read-only metadata tool with no required parameters and annotations covering safety, the description is complete: it tells the agent what will be returned (keys, units, default ranges, tech_values options). The optional `symbol` and `_jq` parameters are fully described in the schema, so nothing needed for invocation 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%, so both `_jq` and `symbol` are already documented in the input schema. The description does not meaningfully add parameter semantics beyond that, so the baseline score 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 opens with a specific verb and resource: 'Get all available screener indicator keys with units and default value ranges.' This clearly identifies the tool as a metadata/reference endpoint and distinguishes it from sibling tools like screener_search and screener_strategy by focusing specifically on indicator keys, units, and ranges.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The use case is implied: call this tool when you need to discover available screener indicators, their units, or default value ranges. However, the description does not explicitly state when not to use it or name alternative tools, so the agent receives no direct routing guidance against siblings.

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

Deploy Server

Screener Indicators

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools