Skip to main content
Glama
longbridge

longbridge

Official

Screener Strategy

screener_strategy
Read-onlyIdempotent

Review filter conditions of a stock screener strategy prior to execution. Retrieve the strategy ID, then run it to find matching stocks.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNo
marketNo

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: -"ScreenerStrategyParam"
  2. 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"
  3. 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"
      +}
  4. Addedv0.4.5

TDQS

A4.3/5.0
Behavior3/5

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

The description aligns with annotations (readOnlyHint, idempotentHint, destructiveHint=false) but does not add additional behavioral details beyond what annotations already provide. With rich annotations, a score of 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 two sentences, front-loaded with the core purpose, and every word is meaningful. No wasted text.

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 parameter and an output schema, the description is complete. It explains what the tool does and how to execute the strategy, and the output schema covers return values.

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 fully describes the single parameter 'id'. The description does not add extra parameter info, so baseline 3 is correct.

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's purpose: 'Inspect a screener strategy's filter conditions before running it.' It uses specific verbs and resources, and distinguishes it from the sibling tool 'screener_search' which executes the strategy.

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?

The description explicitly tells when to use this tool (inspect before running) and provides an alternative: 'Use screener_search strategy_id to execute the strategy.' This clearly differentiates usage scenarios.

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