Skip to main content
Glama

Stocklake — AI Stock Intelligence

by dev.stocklake
OverviewDiscussionsAdmin

Get Indicator History

get_indicator_history
Read-onlyIdempotent

Historical daily indicator snapshots for a stock - ideal for charting and trend detection. Returns up to days days of data (max 730, default 90) from the stock_indicator_snapshots collection which is populated daily by the indicator pipeline.

Every snapshot row contains:

  • recorded_at: ISO date string

  • price: closing price at snapshot time

  • rsi: RSI(14) value (0-100)

  • macd_histogram: MACD histogram value (positive = upward momentum)

  • bb_pct: Bollinger Band % position (0 = at lower, 100 = at upper band)

  • sma20 / sma200: 20-day and 200-day simple moving averages

With full=true, each row also gets:

  • williams_r: Williams %R (0 to -100; >-20 overbought, <-80 oversold)

  • ultimate_osc: Ultimate Oscillator (0-100; >70 overbought, <30 oversold)

  • vix_fix_value: Williams VIX Fix synthetic fear gauge (higher = more fear)

  • williams_ad_trend: Accumulation/Distribution trend (rising/falling/flat)

  • td_signal: DeMark TD Sequential count, named for the move that is running out (DOWNTREND_EXHAUSTION_SETUP / UPTREND_EXHAUSTION_SETUP / DOWNTREND_EXHAUSTION_COUNTDOWN / UPTREND_EXHAUSTION_COUNTDOWN / null)

  • td_phase: DeMark phase (setup_active/setup_complete/countdown_active/countdown_done/null)

  • analyst_rating: analyst consensus (buy/outperform/hold/underperform/sell or null)

  • analyst_target: mean analyst price target or null

Returns {} if fewer than 3 snapshots found. Pro tier only. For informational purposes only. Not financial advice.

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days of historical daily indicator snapshots to return (max 730, default 90). Returns {} if fewer than 3 snapshots are found in the window.
fullNoFalse (default) returns only recorded_at/price/rsi/macd_histogram/bb_pct/sma20/sma200 per day - enough for most charting/trend use. True adds the specialized indicators (williams_r, ultimate_osc, vix_fix_value, williams_ad_trend, td_signal, td_phase) plus analyst_rating/analyst_target, which barely change day to day and roughly double response size over a long window.
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. Changed1 schema field changed
    • changedInput schema / properties / full / description
      Previous value: -"False (default) returns only recorded_at/price/rsi/macd_histogram/bb_pct/sma20/sma200 per day — enough for most charting/trend use. True adds the specialized indicators (williams_r, ultimate_osc, vix_fix_value, williams_ad_trend, td_signal, td_phase) plus analyst_rating/analyst_target, which barely change day to day and roughly double response size over a long window."New value: +"False (default) returns only recorded_at/price/rsi/macd_histogram/bb_pct/sma20/sma200 per day - enough for most charting/trend use. True adds the specialized indicators (williams_r, ultimate_osc, vix_fix_value, williams_ad_trend, td_signal, td_phase) plus analyst_rating/analyst_target, which barely change day to day and roughly double response size over a long window."
  2. Changed1 schema field changed
    • addedInput schema / properties / full
      Added value: +{
+  "default": false,
+  "description": "False (default) returns only recorded_at/price/rsi/macd_histogram/bb_pct/sma20/sma200 per day — enough for most charting/trend use. True adds the specialized indicators (williams_r, ultimate_osc, vix_fix_value, williams_ad_trend, td_signal, td_phase) plus analyst_rating/analyst_target, which barely change day to day and roughly double response size over a long window.",
+  "type": "boolean"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"Number of days of historical daily indicator snapshots to return (max 730, default 90). Returns {} if fewer than 3 snapshots are found in the window."
    • 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."
  4. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: the 730/90 limits, the empty-object return when fewer than 3 snapshots exist, the Pro-tier requirement, and the fact that the pipeline populates it daily.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and constraints are front-loaded, but the long field-by-field enumeration of return values duplicates the output schema, which already exists, so a significant portion of the text does not earn its place against structured data.

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 pro-tier, read-only snapshot tool with a rich output schema, the description covers the operational essentials an agent needs: the empty-result condition, the size cap, the cost of full=true, and the daily refresh cadence.

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 days, full and symbol are already documented in the schema; the description largely restates those semantics (max 730, default 90, what full adds). Baseline 3 applies when the schema does the heavy lifting.

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 and resource ('Historical daily indicator snapshots for a stock') and frames the use case ('charting and trend detection'). It is distinguishable from price-history siblings like get_stock_history, though it never names an alternative explicitly.

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 phrase 'ideal for charting and trend detection' implies a context but gives no when-to-use vs when-not guidance and does not tell the agent how this differs from get_stock_history or get_signals, which an agent must infer.

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