Skip to main content
Glama

Stocklake — AI Stock Intelligence

Get Stock

get_stock
Read-onlyIdempotent

Price, fundamentals, technical indicators, and company profile for a stock. Returns all data needed to understand a stock in a single call.

Key fields:

  • price, change_pct, prev_close, week52_high/low, volume, avg_volume

  • market_cap, enterprise_value, beta

  • pe_trailing, pe_forward, price_to_book, dividend_yield, dividend_rate

  • debt_to_equity, profit_margins, return_on_equity, free_cashflow

  • revenue_growth, earnings_growth, revenue_ttm, gross_profit_ttm

  • analyst_rating: "strong_buy"|"buy"|"hold"|"sell"|"strong_sell" (analyst consensus)

  • analyst_rating_score: 1.0–5.0 mean analyst recommendation (1=strong_buy, 5=strong_sell)

  • analyst_target: mean analyst price target

  • analyst_count: number of analyst opinions

  • indicators: raw RSI, MACD, Bollinger Bands, SMA20/SMA200 (the canonical 50/200-day averages -- no separate top-level ma_50/ma_200 field), EMA20/EMA200, ATR

  • description: company business description

  • website, employees, officers (top 5: name, title, total_pay)

  • updated_at: last data sync timestamp Available to all tiers (raw indicator numbers, no interpretation). This basic six (RSI/MACD/Bollinger/SMA/EMA/ATR) is standard, widely-available technical analysis.

Pro tier also unlocks 6 more specialized indicators inside the SAME indicators block (williams_r, ultimate_osc, vix_fix, williams_ad, td_sequential, elliott_wave -- the Larry Williams family, DeMark TD Sequential, and Elliott Wave) -- these are omitted entirely from the free/guest response (tier-gating sweep, 2026-08-28), not merely unlabeled; free/guest calls get indicators with only the basic six populated.

Pro tier adds four interpreted blocks computed from the same indicators, no extra AI cost, plus a minimum AI-narrative slice — all five below are precomputed, none cost a live AI call:

  • ai_verdict / ai_headline / ai_score / ai_score_band: the minimum useful AI-narrative slice, shared by every pro-tier stock-returning tool. A bare verdict alone isn't actionable (e.g. bearish while up 8% on the day with a strong_buy analyst rating is genuinely ambiguous) — the one-line headline is the "why", ai_score is the 0-100 composite (same scale/band convention as get_signals' signal_score, distinct pipeline). For the full text (summary/key_points/risks/near_term/longer_term) and cross-source news/insider context, call get_stock_research(symbol) instead — that's the only tool with the complete bundle.

  • ai_score (0-100) / ai_score_band (Weak/Moderate/Strong/Very Strong): stock_ai_summary.py's own composite score, on the same 0-100 scale and band boundaries as get_signals()'s signal_score — but a different pipeline/collection, never the same number for the same symbol by coincidence alone.

  • rating: {score 0-10, direction POSITIVE/NEUTRAL/NEGATIVE, signals per-indicator breakdown} — composite technical score

  • signals: flat labeled signals (rsi/macd/bollinger/sma200/sma50/williams_r/ultimate_osc/ vix_fix/williams_ad/td_sequential/elliott_wave, each with a value + plain-English label) — same indicators as 'indicators', pre-interpreted for programmatic use without parsing raw numbers

  • stance_signals: unified list of per-source directional calls (technical rating, AI summary near_term/longer_term, insider/institutional sentiment, analyst consensus, active screener signals) — each entry {stance POSITIVE/NEGATIVE/NEUTRAL, conviction 0-10, horizon INTRADAY/SWING/POSITION/LONG_TERM, edge_quality PROVEN/OBSERVATION/UNKNOWN (per-source signal_backtest track record), source, raw_label, as_of}. Same canonical shape used on the stock detail page — a source with missing/stale data is simply omitted, not nulled out.

  • relative_strength: {windows: {5d/20d/60d/120d/12m -> {stock_return_pct, rs_vs_spy, rs_vs_qqq, rs_vs_sector}}, verdict: one-line plain-language read (e.g. "Laggard — weak near- and long-term")} — stock's own return minus each benchmark's return (percentage points, not a ratio) per window. rs_vs_sector uses the stock's GICS sector SPDR ETF (Vanguard backup if the primary lacks history); omitted for stocks with no resolvable sector (crypto, FX, indices). Windows/ benchmarks with insufficient history are omitted rather than null. null if not precomputed yet.

  • market_risk: {beta_spy_1y, corr_spy_1y} — 1-year daily-return beta and correlation vs SPY. Distinct from quote.beta (Yahoo's own longer-window beta calculation) — this is computed fleet-wide from the same daily bars as relative_strength. Both fields null if not yet precomputed for this symbol (populates on the next scheduled indicators run).

  • forensic_scores: {altman_z, piotroski_f, beneish_m, computed_at} — three classic forensic- accounting formulas (Altman 1968 bankruptcy-risk, Piotroski 2000 fundamental-strength, Beneish 1999 earnings-manipulation-likelihood), computed from balance sheet/income statement/cash flow data, refreshed on each company's own filing cadence (roughly annual). Each sub-block is {score, note, ...} — altman_z adds zone (safe/grey/distress), piotroski_f adds strength (strong/moderate/weak, 0-9 scale), beneish_m adds likely_manipulator (bool, score > -1.78). note explains what the score measures and its known caveats (e.g. Altman Z is not meaningful for banks/insurers and can flag REITs/ client-float businesses as "distress" by design) — always read alongside the score, not in isolation. score: null means genuinely not computable for this company (common for financial-sector names), not an error. No trading signal is derived from these scores anywhere in this API today — treat as raw accounting-model output for your own research.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock ticker symbol. Also accepts a company name as a fallback (e.g. "Apple") when it uniquely resolves to one symbol.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / symbol / description
      Added value: +"Stock ticker symbol. Also accepts a company name as a fallback (e.g. \"Apple\") when it uniquely resolves to one symbol."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description goes well beyond the readOnly/idempotent annotations by disclosing tier-gating behavior, omission semantics ('these are omitted entirely from the free/guest response... not merely unlabeled'), null conventions ('score: null means genuinely not computable'), and the fact that forensic scores are raw accounting-model output with no trading signal derived. It also distinguishes its computed beta from Yahoo's beta, which prevents misinterpretation.

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?

The description is extremely long and contains some redundant or implementation-specific details, such as duplicating the ai_score explanation and including the 'tier-gating sweep, 2026-08-28' note. It is well organized with bullet lists and front-loaded key fields, but it could be trimmed without losing essential guidance.

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?

Given the tool's complexity, the description is remarkably complete. It enumerates return fields, distinguishes free vs Pro response shapes, explains omission/null behavior, names the alternative research tool, and clarifies which values are computed differently from other sources. With an output schema reported present, nothing essential is missing for an agent to select and invoke the tool correctly.

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% and the only parameter, symbol, is already well described in the schema with ticker and company-name fallback behavior. The description adds no additional parameter-level semantics beyond framing the call as a single-snapshot request, so the baseline of 3 applies.

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 clearly states the tool's purpose: 'Price, fundamentals, technical indicators, and company profile for a stock' and says it 'Returns all data needed to understand a stock in a single call.' It also distinguishes itself from the sibling get_stock_research by explicitly naming that tool as the only one with the complete research bundle.

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

Usage Guidelines5/5

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

The description gives explicit routing guidance: for full AI narrative and cross-source news/insider context, call get_stock_research(symbol) instead. It also clarifies tier availability, noting that free/guest responses get only the basic six indicators while Pro unlocks additional blocks, and it stresses that all five Pro blocks are precomputed with no live AI cost.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources