Skip to main content
Glama
Sign In

Stocklake — AI Stock Intelligence

by dev.stocklake
OverviewDiscussionsAdmin

Get Stock News

get_stock_news
Read-onlyIdempotent

Recent news articles for one stock, newest first.

  • symbol: ticker, e.g. "AAPL" or "SAP.DE".

  • days: look-back window in days. Values above the account's maximum are lowered to it (30 or 90 days, depending on the account).

  • limit: max articles returned. Values above the account's maximum are lowered to it (5 or 50 articles, depending on the account).

  • status: "ok" = articles returned | "empty" = no news in the window.

  • Per article: title, published_at. Depending on the account, also ai_sentiment, ai_summary, signal_score (0-100 or null) and signal_score_band ("Weak"/"Moderate"/"Strong"/"Very Strong" or null).

  • signal_score is the same number get_signals() and get_stock_research() report for this symbol when a news-based signal was raised in the last 90 days; otherwise it is computed per article from that article's own classification. It is always a single number.

  • collapsed_count: present when several articles reported the same event (for example one analyst's target change carried by several outlets); only the newest is returned and this says how many were merged into it. limit counts distinct events.

Articles are published by third parties; titles and summaries describe what those articles say. For news together with filings, insider, earnings and analyst events in one timeline, use get_stock_activity. For informational purposes only. Not financial advice.

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days (default 30). Values above the account's maximum (30 or 90) are lowered to it.
limitNoMax articles returned (default 10). Values above the account's maximum (5 or 50) are lowered to it.
symbolYesStock ticker symbol. Also accepts a company name as a fallback when it uniquely resolves to one symbol.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"Look-back window in days. Requesting more than your tier's cap is silently clamped down to it: 30 free/guest, 90 pro."New value: +"Look-back window in days (default 30). Values above the account's maximum (30 or 90) are lowered to it."
    • changedInput schema / properties / limit / description
      Previous value: -"Max articles returned. Default 10 is a Pro-tier-shaped value — on free/guest it's silently clamped down to that tier's cap (5), so a free caller passing no limit effectively gets 5, not 10. Requesting more than your tier's cap (5 free/guest, 50 pro) is likewise clamped down."New value: +"Max articles returned (default 10). Values above the account's maximum (5 or 50) are lowered to it."
  2. Changed3 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"Look-back window in days. Requesting more than your tier's cap is silently clamped down to it: 30 free/guest, 90 pro."
    • addedInput schema / properties / limit / description
      Added value: +"Max articles returned. Default 10 is a Pro-tier-shaped value — on free/guest it's silently clamped down to that tier's cap (5), so a free caller passing no limit effectively gets 5, not 10. Requesting more than your tier's cap (5 free/guest, 50 pro) is likewise clamped down."
    • addedInput schema / properties / symbol / description
      Added value: +"Stock ticker symbol. Also accepts a company name as a fallback when it uniquely resolves to one symbol."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/open-world, but the description adds substantive behavior an agent could not infer: days and limit are silently clamped to account-specific maxima (30/90 and 5/50), status can return 'empty', results are deduplicated by event with collapsed_count, and content is third-party sourced. These are the operational facts that change how an agent interprets and reports 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?

Front-loaded lead sentence followed by a scannable bullet list, with each bullet carrying a distinct operational fact. It runs long and spends several lines describing per-article return fields that the output schema likely already covers, which is the only waste.

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 3-parameter read tool with an output schema, this covers everything: request semantics, clamping, empty-result handling, dedup behavior, the ambiguous signal_score inheritance rule, and a provenance disclaimer. Nothing an agent needs in order to call it and interpret the response is missing.

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

Parameters4/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 real meaning beyond it: concrete ticker examples including a non-US format ('SAP.DE'), restated clamping behavior, and the non-obvious note that 'limit counts distinct events' rather than raw articles. That last point materially affects how an agent sizes its request and is absent from 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?

Opens with a specific verb+resource+scope: 'Recent news articles for one stock, newest first.' The sibling routing line to get_stock_activity makes the boundary explicit, so an agent can distinguish this from get_stock_activity and get_news_feed 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 names the alternative for the adjacent use case ('For news together with filings, insider, earnings and analyst events in one timeline, use get_stock_activity'), which is exactly the routing decision an agent faces. It does not address when to prefer get_news_feed over this per-symbol tool, so the guidance is clear but not exhaustive.

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 toolsInspect
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