Stocklake — AI Stock Intelligence

Get Signals

get_signals

Read-onlyIdempotent

AI-screened stock signals recently surfaced by the Stocklake pipeline — sourced from news analysis, sector screening, and sentiment signals.

Shows what the pipeline noticed in the last 24 hours (falling back to the most recent signals regardless of age if nothing has fired in that window — see window in the response). This reflects what the AI pipeline found, not whether Stocklake's own internal trading engine still holds it live — a signal it later dropped or let expire is still shown here, since that's a fact about our own trading state, not about the signal's informational value.

Parameters:

direction: "POSITIVE" | "NEGATIVE" | "NEUTRAL" (default: all). NEUTRAL covers both a flat/undecided read AND a genuinely two-sided idea (real opposing bull/bear theses on the same symbol) — in the latter case signal_score is the STRONGER of the two sides (see signal_score below), so a high score alongside NEUTRAL means "real conviction here, just no directional consensus," not "nothing going on." The two-sided detail is in rationale.
min_signal_score: minimum composite signal score 0-100 (default 60) — a blend of conviction/confidence/flag_score, source track record, and real technical factors. This is the field to filter on. Always compared against a single number, including for NEUTRAL/two-sided ideas — a result is never returned below your threshold on both sides.
source: filter by signal source — "news" | "screener" | "sentiment" (default: all)
limit: max results to return (default 25, max 50). Each returned signal counts as one call toward your daily limit.

Returns:

count: number of signals returned
window: "24h" (fresh activity found) or a fallback note when the last 24h had nothing and the response instead shows the most recent signals overall
signals[]: each with symbol, direction, signal_score (0-100), signal_score_band (human-readable label — "Weak"/"Moderate"/"Strong"/"Very Strong"), source, rationale, expires, flagged_at

Pro tier only — AI pipeline cost attached. For informational purposes only. Not financial advice.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results to return (default 25, max 50). Each returned signal counts as one call toward your daily limit.
`source`	No	Filter by signal source: "news" \| "screener" \| "sentiment" (default: all).
`direction`	No	Filter by direction: "POSITIVE" \| "NEGATIVE" \| "NEUTRAL" (default: all). NEUTRAL covers both a flat/undecided read and a genuinely two-sided idea (see signal_score below).
`min_signal_score`	No	Minimum composite signal score, 0-100 (default 60) — a blend of conviction/confidence/flag_score, source track record, and real technical factors. This is the field to filter on.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 21, 2026

removedInput schema / properties / min_conviction

Removed value: -{
-  "default": 7,
-  "description": "DEPRECATED, ignored for filtering — kept in the signature only so existing callers don't hard-fail; internal scoring retired the raw conviction/confidence/flag_score triad in favor of signal_score. Passing a non-default value here has no effect and is logged for a planned removal.",
-  "type": "integer"
-}

removedInput schema / properties / min_flag_score

Removed value: -{
-  "default": 8,
-  "description": "DEPRECATED, ignored for filtering — kept in the signature only so existing callers don't hard-fail; internal scoring retired the raw conviction/confidence/flag_score triad in favor of signal_score. Passing a non-default value here has no effect and is logged for a planned removal.",
-  "type": "integer"
-}

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / source / description

Previous value: -"Filter by signal source: \"news\" | \"screener\" | \"sentiment\" | \"social\" (default: all)."New value: +"Filter by signal source: \"news\" | \"screener\" | \"sentiment\" (default: all)."

Changed2 schema fields changedSep 3, 2026

changedInput schema / properties / limit / default
```
Previous value: -50New value: +25
```

changedInput schema / properties / limit / description

Previous value: -"Max results to return (default 50, max 50). Each returned signal counts as one call toward your daily limit."New value: +"Max results to return (default 25, max 50). Each returned signal counts as one call toward your daily limit."

Changed1 schema field changedAug 26, 2026

changedInput schema / properties / direction / description

Previous value: -"Filter by direction: \"POSITIVE\" | \"NEGATIVE\" | \"MIXED\" (default: all)."New value: +"Filter by direction: \"POSITIVE\" | \"NEGATIVE\" | \"NEUTRAL\" (default: all). NEUTRAL covers both a flat/undecided read and a genuinely two-sided idea (see signal_score below)."

Changed6 schema fields changedAug 25, 2026

addedInput schema / properties / direction / description

Added value: +"Filter by direction: \"POSITIVE\" | \"NEGATIVE\" | \"MIXED\" (default: all)."

addedInput schema / properties / limit / description

Added value: +"Max results to return (default 50, max 50). Each returned signal counts as one call toward your daily limit."

addedInput schema / properties / min_conviction / description

Added value: +"DEPRECATED, ignored for filtering — kept in the signature only so existing callers don't hard-fail; internal scoring retired the raw conviction/confidence/flag_score triad in favor of signal_score. Passing a non-default value here has no effect and is logged for a planned removal."

addedInput schema / properties / min_flag_score / description

Added value: +"DEPRECATED, ignored for filtering — kept in the signature only so existing callers don't hard-fail; internal scoring retired the raw conviction/confidence/flag_score triad in favor of signal_score. Passing a non-default value here has no effect and is logged for a planned removal."

addedInput schema / properties / min_signal_score / description

Added value: +"Minimum composite signal score, 0-100 (default 60) — a blend of conviction/confidence/flag_score, source track record, and real technical factors. This is the field to filter on."

addedInput schema / properties / source / description

Added value: +"Filter by signal source: \"news\" | \"screener\" | \"sentiment\" | \"social\" (default: all)."

Changed2 schema fields changedAug 24, 2026
- changedInput schema / properties / limit / default
```
Previous value: -25New value: +50
```
- addedInput schema / properties / min_signal_score
```
Added value: +{
+  "default": 60,
+  "type": "integer"
+}
```
AddedJul 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark the call read-only and idempotent; the description goes beyond them by explaining the 24h fallback window, retention of dropped/expired signals, per-result daily-limit accounting, and the NEUTRAL two-sided semantics. No contradiction with annotations.

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?

The description is lengthy but well structured with scannable sections (purpose, parameters, returns, caveats) and front-loads the core behavior. It is slightly verbose in the caveats, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-optional-parameter read-only tool with an output schema, the description is complete: it covers fallback behavior, direction/score/source semantic nuances, result shape, daily-limit cost, and tier restrictions. An agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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, but the description adds crucial meaning: NEUTRAL covers both flat and two-sided ideas, min_signal_score is always a single-number filter even for two-sided ideas, and limit counts toward the daily call quota. These nuances are not 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 states a specific verb and resource: it returns AI-screened stock signals surfaced by the Stocklake pipeline, naming the three source types (news, screener, sentiment). This clearly differentiates it from sibling tools like get_stock_research or get_news_feed.

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?

It gives clear context for use: retrieve what the AI pipeline noticed in the last 24 hours, with fallback behavior. It does not explicitly name sibling alternatives or spell out when not to use it, but the scope is unambiguous.

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

All Stocklake — AI Stock Intelligence 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?