Skip to main content
Glama
longbridge

longbridge

Official

Top Movers

top_movers
Read-onlyIdempotent

Identify stocks with price moves exceeding 20-day standard deviation and get correlated news reasons. Filter by HK/US/CN/SG markets, sort by time, change magnitude, or popularity.

Instructions

Get stocks whose price fluctuation exceeds the 20-trading-day standard deviation, with correlated news reasons. markets: comma-separated HK/US/CN/SG (omit=all). sort: 0=time 1=change-magnitude 2=popularity/heat (default). limit: results per page (default 20). next_params: pass next_params from previous response to paginate. Returns events[]{timestamp(RFC3339), alert_reason, alert_type, stock{symbol, name, change(decimal ratio e.g. 0.0445=+4.45%), last_done, labels[], intro}}, updated_at, next_params.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketsNoMarket filter: comma-separated list of markets to include. Supported values: "HK", "US", "CN", "SG". Omit to return all markets. Example: "HK,US"
sortNoSort order (default: "2"): "0" = by time (most recent first) "1" = by price change magnitude (largest move first) "2" = by popularity (most-viewed first)
dateNoDate to query in "YYYY-MM-DD" format. Omit for today's movers.
limitNoNumber of events to return per page (default: 20, max: 100)
next_paramsNoPagination cursor from previous response next_params field. Pass the entire next_params object returned by the previous call to get the next page. Omit for the first page.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventsNoMover events.
updated_atNoLast refresh time (RFC3339).
next_paramsNoPagination cursor. Pass back verbatim as `next_params` to fetch the next page. Opaque object — exact fields are an implementation detail.
Behavior4/5

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

Annotations indicate read-only, non-destructive, idempotent, open-world. Description adds beyond annotations by detailing return format (events with fields including timestamp and stock details) and pagination via next_params. 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?

Description is a single paragraph with clear purpose upfront, followed by parameter explanations and return format. It is concise but slightly dense; could be more structured with bullet points.

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?

Given complexity (5 params, nested output), description is thorough. It explains return structure with nested fields (stock, change ratio), pagination, and defaults. Output schema exists, so return details are well-covered.

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?

Input schema descriptions already cover 100% of parameters. Description repeats some parameter info (markets, sort, limit, next_params) but adds minimal extra meaning (e.g., 'date omitted for today'). 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?

Description clearly states the tool's function: getting stocks that exceed 20-day standard deviation in price fluctuation with correlated news. It uses a specific verb 'get' and resource 'stocks with price fluctuation' and distinguishes it from sibling tools like quote or candlesticks.

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?

Description provides operational details (markets, sort, limit, pagination) but does not explicitly guide when to use this tool versus alternatives like 'anomaly' or 'market_temperature'. No when-not-to-use or comparison with siblings.

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