get_technical_indicators

shallow

io.github.aatharva16/dalalos · Verify this server

Get moving averages, RSI, MACD, Bollinger Bands, beta, and circuit-filter band/hit-days for an Indian stock. Accepts NSE symbol, ISIN, or BSE code. Moving averages (sma_50/sma_100/sma_200), `rsi_14` (Wilder's 14-period RSI), `macd` (12/26/9 EMA line/signal/histogram), `bollinger_bands` (20-day, 2-stdev middle/upper/lower + percent_b), and `beta` (regressed against NSE's own Nifty 50 daily close series over the trailing ~1Y of paired trading days; `beta_benchmark` names it) are all mechanically computed from the split/bonus-adjusted daily close series. `circuit_band_pct`/`circuit_band_as_of`/`circuit_hit_days` use the RAW (unadjusted) close series and are NSE's own per-security circuit-filter data, not derived from bhavcopy. NSE publishes only a CURRENT snapshot with no historical archive, so this pipeline's own daily captures are the only source of band history and only exist from whenever this deployment started capturing them: * `circuit_band_pct` is null for TWO DIFFERENT reasons — check `circuit_band_as_of` to tell them apart. `circuit_band_as_of` present + `circuit_band_pct` null means this security genuinely has NSE's "No Band" designation (no static daily price band applies — typically a large/liquid, F&O-eligible name; this is a complete, real answer, NOT missing data). `circuit_band_as_of` null means no band has been captured for this security AT ALL yet (also named in `insufficient_history`) — do not conflate the two. * `circuit_hit_days` is a list of `{trade_date, close, prev_close, pct_change, band_pct}` for RAW-close days that plausibly touched that day's captured band (a small tolerance absorbs NSE's tick-size rounding of the actual limit price off the raw percentage) — a descriptive flag that trading was likely constrained that day, not a claim about why. An indicator needing more history than is cached yet (e.g. sma_200 on a recently-listed stock, beta when too few dates overlap the Nifty 50 series, or circuit-band data for a security with no captured band day yet) is null/empty and named in `insufficient_history` rather than computed or fabricated on a short series. Pure math, no verdicts/signals.

100.0/100

1 trials · measured 41 days ago

get_technical_indicators scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.aatharva16/dalalos, measured 11 Sept 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
gated
Category
Communication
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-09-11100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: get_technical_indicators
[![Vouch score](https://vouch.tools/api/tools/a22a9167-4a2f-42ec-b6ab-637b1c2876b9/badge.svg)](https://vouch.tools/tools/a22a9167-4a2f-42ec-b6ab-637b1c2876b9)
get_technical_indicators — Vouch