Skip to main content
Glama
longbridge

longbridge

Official

Screener Indicators

screener_indicators
Read-onlyIdempotent

Retrieve all screener indicator keys with units, default ranges, and available technical options for filtering stocks.

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
NameRequiredDescriptionDefault
symbolNoOptional security symbol to filter indicators for a specific stock, e.g. "AAPL.US"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupsNo

Schema Changelog

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

  1. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"ScreenerIndicatorsParam"
  2. Changed17 schema fields changedv0.6.0
    • 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"
  3. Changed1 schema field changedv0.5.6
    • 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"
      +}
  4. Addedv0.4.5

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false. The description adds context about the response structure: 'Technical indicators include a tech_values field showing available options'. This explains behavior beyond 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: first clearly states the purpose, second elaborates on a key detail (tech_values structure). No unnecessary words, 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?

Given that output schema exists (stated), the description covers the essential aspects: keys, units, default ranges, and tech_values. Slightly lacking in explaining how defaults are defined or if there are limits, but overall sufficient.

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% with a described optional 'symbol' parameter. The description does not mention the parameter, so it adds no value beyond the schema. 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 clearly states the tool returns 'all available screener indicator keys with units and default value ranges', distinguishing it from sibling tools like screener_search or screener_strategy. The verb 'get' and resource 'indicator keys' are specific.

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 description implies usage when a user needs available screener indicators, but it does not explicitly state when to use this tool versus alternatives (e.g., screener_strategy). No exclusion criteria or comparisons are provided.

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