Skip to main content
Glama
longbridge

longbridge

Official

Top Movers

top_movers
Read-onlyIdempotent

Find stocks whose price change exceeds the 20-day standard deviation and view matched news reasons. Filter by market and sort by time, move size, 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
NameRequiredDescriptionDefault
_jqNoOptional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response.
dateNoDate to query in "YYYY-MM-DD" format. Omit for today's movers.
sortNoSort order (default: "2"): "0" = by time (most recent first) "1" = by price change magnitude (largest move first) "2" = by popularity (most-viewed first)
limitNoNumber of events to return per page (default: 20, max: 100)
marketsNoMarket filter: comma-separated list of markets to include. Supported values: "HK", "US", "CN", "SG". Omit to return all markets. Example: "HK,US"
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.0
    • addedInput schema / properties / _jq / description
      Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."
    • removedInput schema / properties / limit / format
      Removed value: -"uint32"
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -{
      -  "$defs": {
      -    "TopMoverEvent": {
      -      "properties": {
      -        "alert_reason": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "alert_type": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "stock": {
      -          "anyOf": [
      -            {
      -              "$ref": "#/$defs/TopMoverStock"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ]
      -        },
      -        "timestamp": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "TopMoverStock": {
      -      "properties": {
      -        "change": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "intro": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "labels": {
      -          "items": {
      -            "type": "string"
      -          },
      -          "type": [
      -            "array",
      -            "null"
      -          ]
      -        },
      -        "last_done": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "name": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "symbol": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        }
      -      },
      -      "type": "object"
      -    }
      -  },
      -  "properties": {
      -    "events": {
      -      "items": {
      -        "$ref": "#/$defs/TopMoverEvent"
      -      },
      -      "type": [
      -        "array",
      -        "null"
      -      ]
      -    },
      -    "next_params": {},
      -    "updated_at": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  3. Changed3 schema fields changedv0.8.7
    • 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"
      +]
  4. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"StockEventsParam"
  5. Changed16 schema fields changedv0.6.0
    • 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"
  6. Changed1 schema field changedv0.5.6
    • 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"
      +}
  7. Addedv0.4.5

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the selection logic (20-day std dev) and mentions correlated news reasons, but does not describe pagination or response structure. This adds some value beyond annotations but not rich behavioral context.

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 a single efficient sentence, front-loading the core purpose and appending parameter shortcuts. It wastes no words and is easy to scan.

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?

For a read-only tool with full parameter schema coverage, the description adequately conveys the core purpose and selection criteria. It omits details like pagination usage and output format, but these are partially covered by the schema and the tool's simplicity. Given no output schema, a bit more on return values would be ideal, but it is not critical.

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 coverage is 100%, so the baseline is 3. The description repeats parameter hints for markets and sort, but adds no new meaning beyond what the schema provides. It does not mention date, limit, or next_params, which are documented in the schema.

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: retrieving stocks whose price fluctuation exceeds a 20-trading-day standard deviation, with correlated news reasons. This is a specific verb-resource pair and defines the selection criteria, distinguishing it from general screeners like screener_search.

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?

The description does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions. The purpose is clear, but the context for when to choose this over sibling tools like screener_search or candlesticks is only implied, not stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools