longbridge

Official

by longbridge

Overview Schema Source Related Servers Score Discussions(1)Admin

Rust

Hybrid

Top Movers

top_movers

Read-onlyIdempotent

Spot stocks with price moves exceeding 20-day standard deviation, including news reasons. Filter by market (HK/US/CN/SG) and 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).

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	Date to query in "YYYY-MM-DD" format. Omit for today's movers.
`sort`	No	Sort order (default: "2"): "0" = by time (most recent first) "1" = by price change magnitude (largest move first) "2" = by popularity (most-viewed first)
`limit`	No	Number of events to return per page (default: 20, max: 100)
`markets`	No	Market filter: comma-separated list of markets to include. Supported values: "HK", "US", "CN", "SG". Omit to return all markets. Example: "HK,US"
`next_params`	No	Pagination 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

Name	Required	Description	Default
`events`	No
`updated_at`	No
`next_params`	No

Schema Changelog

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

Changed3 schema fields changedv0.8.7Aug 19, 2026

removedInput schema / properties / next_params / additionalProperties
```
Removed value: -true
```

addedInput schema / properties / next_params / properties / visited

Added value: +{
+  "description": "Event IDs already seen in previous pages. Pass back verbatim from the previous response — do not fabricate.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / next_params / required
```
Added value: +[
+  "visited"
+]
```

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"StockEventsParam"
```
Changed16 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / TopMoverEvent / properties / alert_reason / description
```
Removed value: -"Human-readable reason for the alert."
```
- removedOutput schema / $defs / TopMoverEvent / properties / alert_type / description
```
Removed value: -"Alert type/category."
```
- removedOutput schema / $defs / TopMoverEvent / properties / stock / description
```
Removed value: -"The stock that moved."
```
- removedOutput schema / $defs / TopMoverEvent / properties / timestamp / description
```
Removed value: -"Event time (RFC3339)."
```
- removedOutput schema / $defs / TopMoverStock / properties / change / description
```
Removed value: -"Price change (decimal ratio, e.g. 0.0445 = +4.45%)."
```
- removedOutput schema / $defs / TopMoverStock / properties / intro / description
```
Removed value: -"Short company introduction."
```
- removedOutput schema / $defs / TopMoverStock / properties / labels / description
```
Removed value: -"Tag labels associated with the stock."
```
- removedOutput schema / $defs / TopMoverStock / properties / last_done / description
```
Removed value: -"Latest traded price."
```
- removedOutput schema / $defs / TopMoverStock / properties / name / description
```
Removed value: -"Display name of the security."
```
- removedOutput schema / $defs / TopMoverStock / properties / symbol / description
```
Removed value: -"Security symbol, e.g. \"700.HK\"."
```
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / description
```
Removed value: -"Returned by `top_movers`. Wraps an `events` array of stocks whose price\nfluctuation exceeded the 20-trading-day standard deviation, with correlated\nnews reasons, plus pagination metadata. Subset of the wire response."
```
- removedOutput schema / properties / events / description
```
Removed value: -"Mover events."
```
- removedOutput schema / properties / next_params / description
```
Removed value: -"Pagination cursor. Pass back verbatim as `next_params` to fetch the\nnext page. Opaque object — exact fields are an implementation detail."
```
- removedOutput schema / properties / updated_at / description
```
Removed value: -"Last refresh time (RFC3339)."
```
- removedOutput schema / title
```
Removed value: -"TopMoversResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "TopMoverEvent": {
+      "properties": {
+        "alert_reason": {
+          "description": "Human-readable reason for the alert.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "alert_type": {
+          "description": "Alert type/category.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "stock": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/TopMoverStock"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The stock that moved."
+        },
+        "timestamp": {
+          "description": "Event time (RFC3339).",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "TopMoverStock": {
+      "properties": {
+        "change": {
+          "description": "Price change (decimal ratio, e.g. 0.0445 = +4.45%).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "intro": {
+          "description": "Short company introduction.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "labels": {
+          "description": "Tag labels associated with the stock.",
+          "items": {
+            "type": "string"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "last_done": {
+          "description": "Latest traded price.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Display name of the security.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol": {
+          "description": "Security symbol, e.g. \"700.HK\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `top_movers`. Wraps an `events` array of stocks whose price\nfluctuation exceeded the 20-trading-day standard deviation, with correlated\nnews reasons, plus pagination metadata. Subset of the wire response.",
+  "properties": {
+    "events": {
+      "description": "Mover events.",
+      "items": {
+        "$ref": "#/$defs/TopMoverEvent"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "next_params": {
+      "description": "Pagination cursor. Pass back verbatim as `next_params` to fetch the\nnext page. Opaque object — exact fields are an implementation detail."
+    },
+    "updated_at": {
+      "description": "Last refresh time (RFC3339).",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "title": "TopMoversResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The description mentions 'correlated news reasons', which adds some behavioral detail beyond the readOnly annotation. However, it does not disclose pagination behavior (e.g., that next_params is used for paging), or any limitations or edge cases (e.g., how the standard deviation is computed, whether the list is sorted by default). Given the annotations already establish safety, the description adds modest but not comprehensive behavioral insight.

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 concise (two sentences) and front-loads the core purpose. The second sentence listing parameters is somewhat redundant but not overly verbose. It is well-structured but could have been slightly more compact by omitting the redundant parameter details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description provides the key context (unusual price movement threshold) and notes the inclusion of news reasons, but it does not explain the output structure or mention the use of pagination. Given the schema is rich and output schema exists, the missing usage guidance and pagination explanation leave some gaps, but it is not severely incomplete.

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

Parameters2/5

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

The description redundantly repeats the schema descriptions for 'markets' and 'sort' but omits any extra meaning for 'date', 'limit', and 'next_params'. It fails to clarify parameter interactions or defaults beyond what the schema already provides. Since the schema coverage is 100%, the description adds minimal semantic value.

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 function: retrieving stocks with price fluctuations exceeding the 20-trading-day standard deviation, and also mentions that correlated news reasons are included. This is specific and distinct from typical list endpoints, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool compared to other market data tools, such as 'quotes', 'candlesticks', or 'rank_list'. It lacks context about scenarios (e.g., 'use this to identify unusual movers for news analysis') or prerequisites, leaving the agent to infer applicability.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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