MoveSurge

Biggest measured movers

top_movers

Read-only

Rank price moves around news among the newest 400 eligible events in the window. Includes each sample's time window and quality notes. This is not a full-market daily gainers/losers list; scan reports the coverage limit.

Input Schema

Name	Required	Description
`hours`	No	Look-back window in hours (1-336, default 24).
`limit`	No	Max results (1-50, default 10).
`end_utc`	No	Exclusive end timestamp with timezone. Overrides the relative look-back window.
`start_utc`	No	Inclusive start timestamp with timezone, e.g. 2026-10-14T00:00:00-04:00.
`min_move_pct`	No	Minimum absolute move percent (default 0.5).

Output Schema

Name	Required	Description
`scan`	No
`count`	Yes
`error`	No
`movers`	Yes	Ranked by the largest absolute measured move, biggest first.
`as_of_utc`	No
`data_note`	No
`data_status`	No
`min_move_pct`	No
`query_window`	No
`window_hours`	No
`withheld_rows`	No
`returned_counts`	No
`newest_result_utc`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 19, 2026
- addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / movers / items / properties / related_companies
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / properties / movers / items / properties / screen_matches
```
Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / withheld_rows
```
Added value: +{
+  "type": "object"
+}
```
Changed21 schema fields changedOct 18, 2026
- addedInput schema / properties / end_utc
```
Added value: +{
+  "description": "Exclusive end timestamp with timezone. Overrides the relative look-back window.",
+  "type": "string"
+}
```
- addedInput schema / properties / start_utc
```
Added value: +{
+  "description": "Inclusive start timestamp with timezone, e.g. 2026-10-14T00:00:00-04:00.",
+  "type": "string"
+}
```
- addedOutput schema / properties / as_of_utc
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data_note
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data_status
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / movers / items / properties / market_reaction / properties / instruments / items / properties / baseline_kind
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / movers / items / properties / market_reaction / properties / instruments / items / properties / baseline_utc
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / movers / items / properties / market_reaction / properties / instruments / items / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / movers / items / properties / market_reaction / properties / instruments / items / properties / notes
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / movers / items / properties / market_reaction / properties / instruments / items / properties / samples
```
Added value: +{
+  "items": {
+    "properties": {
+      "change_pct": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "minutes": {
+        "type": "integer"
+      },
+      "price": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "sample_utc": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / movers / items / properties / market_reaction / properties / instruments / items / properties / session
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / movers / items / properties / market_reaction / properties / instruments / items / properties / volume
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / movers / items / properties / market_reaction / properties / interpretation
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / movers / items / properties / price_data_status
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / movers / items / properties / published_et
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / movers / items / properties / read_through
```
Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / movers / items / properties / url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
- addedOutput schema / properties / newest_result_utc
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / query_window
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / properties / returned_counts
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / properties / scan
```
Added value: +{
+  "type": "object"
+}
```
First observedOct 2, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond that: the coverage cap of 400 newest eligible events, that results include per-sample time windows and quality notes, and that the scan reports its coverage limit — important caveats about data completeness for a ranking tool.

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?

Three sentences, front-loaded with the core action and scope, with no filler. The final clause about the coverage limit is slightly redundant with the earlier 'newest 400 eligible events' statement, which keeps it just short of a 5.

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?

With an output schema present, return values need not be explained, and annotations cover the safety profile. The description supplies the missing pieces an agent needs — the coverage cap, quality caveats, and the anti-scope warning — though it stops short of naming the alternative tools for full routing completeness.

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 description coverage is 100%, so all five parameters (hours, limit, end_utc, start_utc, min_move_pct) are already documented with ranges and defaults. The description references a 'window' but adds no syntax, precedence, or interaction detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Rank price moves around news') plus a precise scope ('newest 400 eligible events in the window'). It distinguishes itself from a generic gainers/losers list, though it does not name the closest siblings such as explained_moves or coverage_stats, so an agent still has to infer routing among them.

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?

Usage is only implied through the negative statement 'This is not a full-market daily gainers/losers list', which is not one of the sibling tools. There is no explicit when-to-use or 'use X instead' guidance relative to explained_moves, event_screen, or coverage_stats, so an agent gets partial but incomplete routing help.

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

All MoveSurge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?