MoveSurge

Search market headlines

search_headlines

Read-only

Search real-time financial news by words or ticker. Returns dated headlines, links and available prices before and after the news. All query words must match, in any order. Use start_utc/end_utc for a specific date. A price move alone does not prove the cause.

Input Schema

Name	Required	Description
`hours`	No	Look-back window in hours (1-336, default 24).
`limit`	No	Max results (1-50, default 20).
`query`	No	Words to match in the headline, all required, any order (maximum 8).
`impact`	No	Optional existing event-impact classification.
`ticker`	No	Restrict to a ticker, e.g. NVDA.
`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.
`before_hours`	No	End the window this many hours ago; use with hours to inspect earlier parts of the day.

Output Schema

Name	Required	Description	Default
`count`	Yes
`error`	No
`as_of_utc`	No
`data_note`	No
`headlines`	Yes
`data_status`	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 / headlines / items / properties / related_companies
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / properties / headlines / 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"
+}
```
- changedInput schema / properties / query / description
```
Previous value: -"Free text to match in the headline."New value: +"Words to match in the headline, all required, any order (maximum 8)."
```
- 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 / headlines / items / properties / market_reaction / properties / instruments / items / properties / baseline_kind
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / headlines / items / properties / market_reaction / properties / instruments / items / properties / baseline_utc
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / headlines / items / properties / market_reaction / properties / instruments / items / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / headlines / items / properties / market_reaction / properties / instruments / items / properties / notes
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / headlines / 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 / headlines / items / properties / market_reaction / properties / instruments / items / properties / session
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / headlines / items / properties / market_reaction / properties / instruments / items / properties / volume
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / headlines / items / properties / market_reaction / properties / interpretation
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / headlines / items / properties / price_data_status
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / headlines / items / properties / published_et
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / headlines / items / properties / read_through
```
Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / headlines / 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.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description goes beyond them by disclosing the return contents and adding the interpretive caveat 'A price move alone does not prove the cause', which is genuinely useful context for an agent reasoning over results.

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?

Four short sentences, front-loaded with the core verb/resource and return shape, with the caveat last. Dense and largely waste-free, though the matching-rule sentence partly duplicates the schema.

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, the description needn't document return fields, yet it still summarizes them. All 8 parameters are optional and fully schema-documented, so an agent has enough to call it correctly; only cross-tool routing remains thin.

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 the baseline is 3. The description restates the AND-matching rule the schema already documents and only lightly adds that start_utc/end_utc can pin a specific date, without clarifying interaction with hours/before_hours or the impact enum.

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 ('Search real-time financial news by words or ticker') and even previews the return shape (dated headlines, links, pre/post prices). It does not explicitly distinguish itself from close siblings such as get_article or explained_moves, so it stops short of a 5.

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?

It gives parameter-selection guidance ('Use start_utc/end_utc for a specific date') and matching semantics, which implies the search use case. However, it never says when to prefer this tool over explained_moves, event_screen, or get_article, so the routing guidance is only implied.

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?