Skip to main content
Glama
longbridge

longbridge

Official

Screener Search

screener_search
Read-onlyIdempotent

Filter stocks across US, HK, CN, SG markets using fundamental or technical conditions. Use a saved strategy or define custom criteria.

Instructions

Screen stocks. market: US|HK|CN|SG (Mode B required; Mode A uses strategy's market). Mode A: strategy_id from screener_recommend_strategies — auto-runs saved strategy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 0-based (default: 0)
sizeNoPage size (default: 20, max: 100)
marketNoMarket: "US" | "HK" | "CN" | "SG". Mode A: overridden by the market embedded in the strategy; pass any value or omit. Mode B: required — determines which market to screen.
conditionsNoMode B — Filter conditions as objects, passed directly to the API. Each item: {"key": "KEY", "min": "10", "max": "50", "tech_values": {}} The "filter_" prefix is added automatically to the key if missing. Fundamental keys (pass with or without filter_ prefix): pettm pbmrq roe roa netmargin salesgrowthyoy netincomegrowthyoy marketcap(亿) circulating_marketcap(亿) prevclose prevchg(%) divyld la epsttm netincome(亿) sales(亿) turnover_rate balance(万) Technical indicator keys (tech_values required; call screener_indicators for schema): macd_day/week → {"category":"goldenfork"|"deadcross","period":"day"|"week"} rsi_day/week → {"value_type":"overbought"|"oversold"} kdj_day/week → {"category":"goldenfork"|"deadcross"} boll_day/week → {"category":"breakthrough_up"|"breakthrough_down"}
sort_orderNoSort order: "asc" | "desc" (default: "desc")
sort_by_keyNoIndicator key to sort results by (e.g. "marketcap", "roe"). Defaults to the first condition key. Must be one of the condition or extra_returns keys.
strategy_idNoMode A — Strategy ID from screener_recommend_strategies screeners[].id. The tool auto-fetches the strategy and builds filters. Omit for Mode B.
extra_returnsNoExtra indicator keys to include in each result row (display-only, not used as filters). Same key naming as conditions (filter_ prefix added automatically). Example: ["marketcap", "prevclose", "epsttm"]

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNo
totalNo
Behavior4/5

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

Annotations already indicate this is read-only (readOnlyHint=true) and non-destructive (destructiveHint=false). The description adds behavioral context: Mode A auto-runs a saved strategy, and Mode B requires a market. No contradictions. Pagination or rate limits are not mentioned but are covered by annotations like openWorldHint.

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 extremely concise—two sentences with no wasted words. The first sentence states the core purpose, the second elaborates on the two modes. Front-loaded and easy to parse.

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 the tool's complexity (8 parameters, two modes) and the existence of an output schema, the description covers the essential usage contexts. It does not detail every parameter but the schema provides that. Some missing context like result format or pagination is acceptable because the output schema exists. Overall, adequate for an experienced user.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All parameters are fully described in the schema (coverage 100%), so the description adds value by explaining the mode-dependent behavior of 'market' and 'strategy_id' parameters. This context goes beyond the schema descriptions, clarifying when each parameter is required and how it interacts.

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 screens stocks and specifies market options (US|HK|CN|SG). It distinguishes two modes: Mode B for direct market screening and Mode A using a saved strategy from screener_recommend_strategies, which differentiates it from sibling tools like screener_indicators or screener_strategy.

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 explains the two contexts for using each mode: Mode A when a saved strategy is available, Mode B for custom screening with market required. It implicitly connects to screener_recommend_strategies but does not explicitly state when not to use this tool or compare to alternatives like screener_strategy.

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