Skip to main content
Glama

Technical Snapshot

tt_indicator_snapshot
Read-onlyIdempotent

Where an instrument is RIGHT NOW on the standard technicals — and what happened the last N times it read the same way.

Returns THREE verdicts, not one: summary, moving averages, oscillators. They disagree by construction in a strong move — moving averages follow the trend, oscillators fade it — so a single blended gauge reports "Neutral" during a screaming rally. When divergent is true, say which half is which; that is the useful sentence.

signal_history walks the same bars back, finds every prior time this instrument printed this verdict on this timeframe, and reports the distribution of what followed at 1h / 3h / one session. Forward moves are measured from the NEXT bar's OPEN — the first price actually tradeable after the reading — never from the close that produced it. Consecutive bars in one state collapse to a single occurrence.

ALWAYS quote the sample size with any hit rate, and when thin_sample is true say the sample is too small to lean on. The bars come from the same store the backtest engine runs on, which is why the reading and its history are comparable at all.

This is MARKET DATA, NOT ADVICE. The verdict is a tally of indicator states. Never render it as a recommendation to buy, sell, enter or exit.

Works on both venues: Indian roots (NIFTY 50, NIFTY BANK, SENSEX, ...) and US roots (SPX, SPY, QQQ, ...). Timeframes: 1m, 3m, 5m, 15m, 30m, 1h — daily is deliberately absent because a UTC-bucketed day splits an Indian session. No auth required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "underlying": "<underlying>"
    },
    "name": "tt_indicator_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
historyNo
timeframeNoOne of: 1m, 3m, 5m, 15m, 30m, 1h. Default '5m'.5m
underlyingYes
lookback_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only cover the read-only/idempotent/open-world safety profile, and the description adds substantial behavior on top: the three-verdict structure and why the halves disagree, forward returns measured from the NEXT bar's open rather than the signal close, consecutive same-state bars collapsed to one occurrence, and the shared data store that makes reading and history comparable. These are exactly the mechanics an agent needs and cannot get from 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 what-it-is sentence is front-loaded and the divergent-verdict explanation is the most useful content placed early. The piece is long, and the 'ALWAYS quote the sample size' instruction plus the market-data-not-advice disclaimer sit closer to agent-output policy than to tool selection, but nearly every sentence carries information an agent would otherwise have to guess.

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

Completeness4/5

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

With no output schema, the description does the work of explaining return values (three verdicts, signal_history distribution at 1h/3h/one session, divergent, thin_sample) and does it well. The remaining gap is parameter-side: `history` and `lookback_days` semantics are not spelled out, which matters for a four-parameter tool.

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 only 25%, so the description must carry parameter meaning; it partly does — it enumerates the timeframe set, names example roots for `underlying` on both venues, and implies `lookback_days` via 'walks the same bars back'. But the `history` boolean is never mentioned, and `lookback_days` units/behavior and accepted underlying symbol format are left implicit.

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 opening line names a specific resource and scope: a current read of an instrument's standard technicals plus the distribution of what followed the last N times it read the same way. The description of three simultaneous verdicts (summary, moving averages, oscillators) and the signal_history walk-back makes it impossible to confuse with the strategy/backtest siblings.

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 explicit application rules — always quote sample size, flag thin_sample, name which half of a divergent reading is which, never render as a recommendation — plus scope constraints (both venues, six intraday timeframes, daily deliberately excluded, no auth). It stops short of naming a sibling alternative or an explicit 'use this instead of X when...' condition, so it is clear context rather than full routing guidance.

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