MoveSurge

Ticker event history

ticker_history

Read-only

Recent tape events for one ticker with each event's measured reaction. Use to answer 'what has been driving lately'.

Input Schema

Name	Required	Description
`days`	No	Look-back window in days (1-60, default 7).
`limit`	No	Max results (1-50, default 20).
`ticker`	Yes	Ticker symbol, e.g. WDAY.
`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.

Output Schema

Name	Required	Description	Default
`error`	No
`events`	No
`ticker`	No
`as_of_utc`	No
`data_note`	No
`data_status`	No
`window_days`	No
`query_window`	No
`withheld_rows`	No
`returned_counts`	No
`newest_result_utc`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026
- addedOutput schema / properties / events / items / properties / related_companies
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / properties / events / items / properties / screen_matches
```
Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / withheld_rows
```
Added value: +{
+  "type": "object"
+}
```
Changed20 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 / events / items / properties / market_reaction / properties / instruments / items / properties / baseline_kind
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / events / items / properties / market_reaction / properties / instruments / items / properties / baseline_utc
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / events / items / properties / market_reaction / properties / instruments / items / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / events / items / properties / market_reaction / properties / instruments / items / properties / notes
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / events / 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 / events / items / properties / market_reaction / properties / instruments / items / properties / session
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / events / items / properties / market_reaction / properties / instruments / items / properties / volume
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / events / items / properties / market_reaction / properties / interpretation
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / events / items / properties / price_data_status
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / events / items / properties / published_et
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / events / items / properties / read_through
```
Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / events / 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"
+}
```
First observedOct 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description's only added behavioral payload is that each event comes with a measured reaction, which is a modest but real disclosure about the returned data shape; limits, defaults, and window behavior are left to the schema.

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?

Two short sentences, zero filler, with the resource and scope stated first and the use case second. Nothing could be removed without losing meaning.

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 annotations covering the safety profile, a 100%-documented input schema, and an output schema that carries return-value detail, the description only needs to convey purpose, scope, and use case — all of which it does. The remaining gap is sibling disambiguation against the other event/move tools, which is a usage-routing concern rather than a completeness failure.

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% for all five parameters (days, limit, ticker, end_utc, start_utc), including ranges, defaults, and the fact that end_utc overrides the relative window. The description adds no parameter meaning beyond the schema, so the baseline 3 is appropriate.

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?

States a specific verb+resource pair: recent tape events scoped to a single ticker, with the added detail that each event carries a 'measured reaction.' That is far more informative than the title alone, but it never distinguishes itself from close siblings such as explained_moves or event_screen, so the agent must still infer which of the overlapping history tools to pick.

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 sentence "Use to answer 'what has been driving <ticker> lately'" gives an explicit usage context, which is better than nothing. However, it names no alternatives and no when-not condition, and the sibling set (explained_moves, event_screen, top_movers) clearly overlaps with this scenario, leaving the routing decision implied rather than stated.

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?