Skip to main content
Glama

Live Straddle Price

tt_straddle_live
Read-onlyIdempotent

What the ATM straddle is worth RIGHT NOW, and what it has done since today's open, in rupees (or dollars), minute by minute.

WHICH OF THE THREE: tt_straddle_chart is the one contract for a SESSION's line, today or a past date — reach for it first, including for a past session. This tool is the live minute-by-minute read of TODAY and takes no date. tt_straddle_decay is the HISTORICAL PROFILE across many sessions (percent of each session's open), not a chart of one. It reads the ENGINE'S OWN live tick store, so it sees today; the historical companion tt_straddle_decay reads the nightly backtest store and cannot.

USE THIS when the question is about NOW or TODAY ("what's the straddle at", "how much has it decayed today", "is premium holding up"). USE tt_straddle_decay when the question is about the PATTERN across many sessions, or about any PAST date — passing it a date returns this exact absolute-price shape for that session.

Returns the minute series plus the numbers that belong beside it: strike, CE and PE separately, spot, SYNTHETIC FUTURE (strike + CE - PE, the forward the options are pricing — quote it next to spot when they diverge), days to expiry, open/high/low, and the time of the last point. expiry (YYYY-MM-DD) and strike are optional; the nearest quoting expiry and the ATM strike are used by default, and available_expiries lists the rest.

Say the time of the last point rather than implying a close — this moves. MARKET DATA, NOT ADVICE. 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_straddle_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
expiryNoYYYY-MM-DD; omit for the nearest quoting expiry.
strikeNoOmit or 0 for the ATM strike.
underlyingYes
bucket_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world behavior, and the description adds what they can't: the data source (the engine's own live tick store vs the nightly backtest store), the freshness caveat ('this moves', quote the last point's time), and that no auth is required. It also discloses the returned fields, which is above the bar given a lower burden 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?

Well front-loaded with headers and the routing comparison placed before the return description. Slightly redundant: the past-date behavior of the siblings is stated once under 'WHICH OF THE THREE' and again under 'USE tt_straddle_decay when', which could be compressed without losing meaning.

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 4-parameter tool with no output schema, the description covers return contents thoroughly (strike, CE/PE, spot, synthetic future, DTE, OHLC, timestamp, available_expiries) and warns about staleness. The one real hole is bucket_minutes, left undocumented in both description and schema.

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 coverage is only 50%. The description compensates for two parameters by explaining that expiry defaults to the nearest quoting expiry and strike defaults to ATM, and that available_expiries lists alternatives. It says nothing about bucket_minutes, which materially changes the series granularity, and nothing about underlying beyond implication.

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 resource and scope: the ATM straddle's live value RIGHT NOW, plus its intraday path, in currency units, minute by minute. It explicitly positions itself against tt_straddle_chart and tt_straddle_decay, so an agent can pick without opening schemas.

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?

Explicit routing rules: use this for questions about NOW or TODAY, reach for tt_straddle_chart first for a single session (today or past), and use tt_straddle_decay for the multi-session historical profile or any past date. Concrete example phrasings ('what's the straddle at', 'is premium holding up') remove inference.

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