Skip to main content
Glama
longbridge

longbridge

Official

Screener Search

screener_search
Read-onlyIdempotent

Filter stocks across US, HK, CN, and SG markets by fundamental and technical criteria. Use saved strategies or define custom conditions with keys like PE ratio, RSI, and MACD.

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. Mode B: conditions=[{"key":"KEY","min":"10","max":"50","tech_values":{}},...]. extra_returns=["key",...] adds display-only columns. sort_by_key: key name to sort by; sort_order: asc|desc (default desc). page: 0-based (default 0). Returns {total, items[]{symbol, name, indicators[]{key, name, value, unit}}}. Fundamental keys: pettm pbmrq roe roa netmargin salesgrowthyoy netincomegrowthyoy marketcap(亿) circulating_marketcap(亿) prevclose prevchg(%) divyld la epsttm netincome(亿) sales(亿) turnover_rate balance(万). Technical keys (call screener_indicators for tech_values schema): macd_day/week rsi_day/week kdj_day/week boll_day/week.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
strategy_idNoMode A — Strategy ID from screener_recommend_strategies screeners[].id. The tool auto-fetches the strategy and builds filters. Omit for Mode B.
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"}
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"]
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.
sort_orderNoSort order: "asc" | "desc" (default: "desc")
pageNoPage number, 0-based (default: 0)
sizeNoPage size (default: 20, max: 100)
Behavior4/5

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

Annotations already indicate read-only, idempotent, open-world. The description adds value by detailing return structure (total, items with indicators), the automatic 'filter_' prefix for condition keys, and that extra_returns are display-only. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is information-dense but well-structured: opening with purpose, then mode breakdown, parameter details, and key lists. Front-loaded with critical mode distinction. Could be slightly more concise but effectively uses every sentence.

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 8 parameters, two modes, and many keys, the description is thorough: covers all parameters, return format, key lists, and ties to sibling tools. No output schema, so return structure is adequately described. Minor omission: no explicit max page size noted in description (but schema has it).

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

Parameters5/5

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

Schema coverage is 100%, but description adds significant meaning: explains mode-dependent behavior for market, lists all fundamental and technical keys with examples, describes sort defaults and pagination. This goes well beyond schema descriptions.

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 states 'Screen stocks' and specifies markets US|HK|CN|SG. It clearly distinguishes two modes: Mode A for saved strategies (referencing sibling screener_recommend_strategies) and Mode B for custom conditions. This differentiates from other screener tools and provides specific verb+resource.

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 when to use Mode A (strategy_id from screener_recommend_strategies) and Mode B (custom conditions), including prerequisites. It references calling screener_indicators for tech_values schema, aiding correct usage. Lacks explicit 'when not to use' but covers alternatives well.

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