Skip to main content
Glama

Straddle Decay Chart

tt_straddle_decay
Read-onlyIdempotent

How an ATM straddle's PREMIUM behaves through a trading session, ACROSS MANY SESSIONS — the decay PROFILE, for both Indian and US markets. Its curve is a percent of each session's own open, not money, and the multi-session profile returns a hosted chart (chart_url) plus the numbers behind it; a single-session call returns prices and no chart.

For one session's line in rupees or dollars — today or a past date — use tt_straddle_chart. This is the tool for "what does decay usually look like", not "what did it do on the 2nd".

INDIA: NIFTY (say "NIFTY 50" or "NIFTY"), BANKNIFTY ("NIFTY BANK"), FINNIFTY, MIDCPNIFTY, SENSEX, BANKEX — NSE/BSE minute bars from 2020-01-01, the same store the backtest engine reads.

US: SPX, XSP, NDX, VIX and SPY, QQQ, IWM, GLD, DIA, TQQQ, AAPL, TSLA, NVDA, GOOGL, AMZN, META, MSFT, AMD, PLTR, NFLX, INTC, GOOG — OPRA minute bars from 2021-08-16.

TWO MODES. Pass date (YYYY-MM-DD) for ONE session's curve. Omit it for the HISTORICAL profile over sessions trading days ending at end_date (sessions 0 = pick by expiry cadence: 60 for the daily names, 20 for a weekly like NIFTY or SENSEX, 12 for a monthly — so the WINDOW is comparable rather than the count; ask for more explicitly if you want it) (default: the latest session) — median premium by time of day with a 25th-75th percentile band, the median full-day decay, how often the premium finished lower than it opened, and when it typically bottoms.

dte is days to expiry: 0 (default) is the NEAREST real expiry. That is same-day where options expire daily (SPX/SPY/QQQ); in India, post-SEBI, only NIFTY and SENSEX carry a weekly (NIFTY expires TUESDAY) and the rest are monthly, so a 0DTE profile there samples expiry days only — which is correct: blending a 0DTE curve with a 6DTE one describes no tradeable thing. The ATM strike is fixed at the session open and every curve value is a PERCENT OF THAT SESSION'S OPENING PREMIUM.

A RISING LINE MEANS PREMIUM EXPANDED, not a loss — the straddle gains when the underlying outruns time decay. This is market data, not a position: never present it as P&L, and never turn it into advice to sell or buy straddles.

Sessions are aligned on the venue's OWN wall clock — Eastern for the US (so summer and winter sessions superimpose despite DST) and IST for India — and early-close half-days are excluded unless include_half_days is set. Indian bars end 15:30 IST: NSE has run F&O to 15:40 since 2026-08-03 and those minutes are not imported, so say so rather than implying the curve runs to the real close. No auth required — this is market data, not account data.

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_straddle_decay"
  }
}

Input Schema

NameRequiredDescriptionDefault
dteNo
dateNoYYYY-MM-DD for ONE session's curve; omit for the series.
end_dateNo
sessionsNoSessions to cover. 0 picks by expiry cadence: 60 for the daily names, 20 for a weekly like NIFTY or SENSEX, 12 for a monthly.
underlyingYes
bucket_minutesNo
include_half_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnly/openWorld/idempotent annotations, it discloses that curve values are percent of each session's opening premium, that multi-session returns a hosted chart_url while single-session returns prices only, and that a rising line means premium expansion not loss. It also documents data provenance and cutoffs (NSE/BSE from 2020-01-01, OPRA from 2021-08-16), DST-safe wall-clock alignment, half-day exclusion, and the 15:30 IST bar-end caveat.

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?

Front-loaded and information-dense, but it is very long, uses heavy parenthetical nesting, and restates the two-mode behavior in both the opening paragraph and the TWO MODES paragraph. The all-caps emphasis on several lines adds noise rather than clarity.

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?

For a 7-parameter, no-output-schema analytics tool this is nearly complete: return shape (chart_url plus underlying numbers, or prices), market coverage, expiry cadence, and known data caveats are all covered. The only material omission is any explanation of `bucket_minutes` and how it affects the curve resolution.

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?

With only 29% schema coverage, the description carries the load and largely does: it explains `date` semantics, `end_date`, `dte` (0 = nearest real expiry, with per-market expiry cadence), `sessions` (0 = cadence-based window, 60/20/12), `include_half_days`, and enumerates valid `underlying` values per market. The gap is `bucket_minutes`, which is neither in the schema description nor the description text.

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?

States a specific verb+resource: how an ATM straddle's premium behaves across many sessions, i.e. the decay profile. It explicitly separates itself from tt_straddle_chart (single-session line) and from tt_straddle_live by framing the question as 'what does decay usually look like' vs 'what did it do on the 2nd'.

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?

Gives explicit routing rules: pass `date` for one session, omit it for the historical profile, and use tt_straddle_chart for a single session's line in rupees or dollars. It also sets a usage boundary by forbidding P&L framing or buy/sell advice, and notes no auth is required.

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