MoveSurge

Watchlist digest

watchlist_digest

Read-only

Check up to 25 tickers in one call: for each, how many headlines crossed in the window, the latest ones with the stock's own measured price move, and its largest move; which names were quiet and when they last had news; and who reports earnings in the next 14 days. Use for a morning or nightly watchlist check instead of one call per ticker.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tickers": "<tickers>"
    },
    "name": "watchlist_digest"
  }
}

Input Schema

Name	Required	Description
`hours`	No	Look-back window in hours (1-168, default 24).
`end_utc`	No	Exclusive end timestamp with timezone. Overrides the relative look-back window.
`tickers`	Yes	Up to 25 ticker symbols, e.g. ["NVDA", "MSFT", "TSM"].
`start_utc`	No	Inclusive start timestamp with timezone, e.g. 2026-10-14T00:00:00-04:00.
`headlines_per_ticker`	No	Headlines shown per active ticker (1-5, default 3).

Output Schema

Name	Required	Description
`scan`	No
`basis`	No
`error`	No
`quiet`	Yes
`active`	Yes
`upcoming`	Yes
`as_of_utc`	No
`data_note`	No
`follow_url`	No	Page where the user can get these tickers' headlines by email each US trading day.
`data_status`	No
`query_window`	No
`window_hours`	No
`withheld_rows`	No
`returned_counts`	No
`newest_result_utc`	No
`tickers_requested`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the safety profile is covered; the description adds the batching ceiling (25 tickers), the composition of the digest, and the fixed 14-day earnings look-ahead, which is behaviorally important and not derivable from the schema. It does not discuss cost/rate limits or output ordering, keeping it out of 5 territory.

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?

Two sentences, front-loaded with the key capability and followed by the intended usage. The middle enumeration is dense and clause-heavy but every item corresponds to real returned content, so little is wasted; only minor tightening is possible.

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 and full parameter documentation, the description only needs to orient the agent, which it does: batch size, window semantics, digest contents, and the use case. Nothing essential is missing, though a note on relative cost versus per-ticker calls would make the routing decision airtight.

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 hours, start_utc/end_utc, tickers, and headlines_per_ticker are all documented in the schema itself. The description only reinforces the 25-ticker cap and the notion of a look-back 'window' without adding format or interaction details (e.g. how start_utc/end_utc override hours). Baseline 3 is appropriate.

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?

States a specific verb and scope ('Check up to 25 tickers in one call') and then enumerates exactly what comes back: headline counts, latest headlines with measured price moves, largest move, quiet names with last-news time, and upcoming earnings. This is clearly distinguishable from single-ticker siblings like ticker_brief or search_headlines without opening any schema.

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

Usage Guidelines4/5

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

Explicitly frames the use case ('a morning or nightly watchlist check') and names the alternative pattern it replaces ('instead of one call per ticker'). It stops short of naming a specific sibling tool or stating when-not to use it (e.g. when to prefer ticker_brief for a deep single-name dig), so it falls just short of a 5.

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?