Skip to main content
Glama

Straddle Chart

tt_straddle_chart
Read-onlyIdempotent

The straddle chart — ATM straddle price through ONE session, in rupees (or dollars). Today by default; any past session with date. This is the tool for a session's line; tt_straddle_live is today's live minute-by-minute read, and tt_straddle_decay is the historical profile across many sessions.

Prefer this over tt_straddle_live / tt_straddle_decay for anything chart-shaped: it is one contract for both, so "what's the straddle now" and "show me 2nd September" return the same fields and the caller does not branch.

date omitted / "today" -> live, from the engine's tick store date = YYYY-MM-DD -> that completed session expiry = YYYY-MM-DD -> a specific expiry (default: the nearest)

band adds the same instrument's own history behind the line — the usual range at the SAME days-to-expiry, ending the day before, and already scaled to this session's open so it can be drawn on the same axis without converting anything. With it comes context, whose sentence says whether the session is decaying faster, slower or in line with usual.

The strike is anchored to the FORWARD, not spot — that is what at-the-money means for an option, and it differs from the cash strike on most non-expiry days.

Use tt_straddle_decay when the question is about the PATTERN across many sessions rather than one chart. MARKET DATA, NOT ADVICE. No auth.

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

Input Schema

NameRequiredDescriptionDefault
bandNo
dateNoYYYY-MM-DD for one completed session; omit (or 'today') for the live curve from the engine's tick store.
expiryNoYYYY-MM-DD for a specific expiry; omit for the nearest.
underlyingYes
band_sessionsNo
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 declare readOnly/idempotent/non-destructive, but the description adds real behavioral context: date omitted pulls live ticks from the engine's store, `band` overlays history scaled to this session's open, `context.sentence` reports faster/slower/in-line decay, and the strike is forward-anchored not spot. It also states 'MARKET DATA, NOT ADVICE. No auth.', which annotations do not convey.

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?

Front-loads the core definition and then organizes date-mode behavior in an indented block, which is easy to scan. It is somewhat prose-heavy and the 'caller does not branch' aside is mildly verbose, but nearly every sentence carries routing or behavioral information.

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?

There is no output schema, so the description must explain returns; it does this partially by naming the fields (`band`, `context.sentence`) and asserting both chart modes return the same fields. For a 6-parameter tool it still leaves `band_sessions` and `bucket_minutes` unexplained, keeping it short of complete.

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 33%, so the description must compensate. It explains `date` semantics well (omitted/today -> live from tick store, YYYY-MM-DD -> completed session), `expiry` (default nearest), and `band` in detail, but leaves `underlying`, `band_sessions`, and `bucket_minutes` completely undocumented in both schema and description.

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: ATM straddle price for ONE session, in rupees/dollars, with today as default and any past session via `date`. It explicitly names and contrasts the two siblings (tt_straddle_live, tt_straddle_decay) so the agent can distinguish 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?

Gives explicit routing: 'This is the tool for a session's line', live is 'today's live minute-by-minute read', decay is 'the historical profile across many sessions'. It adds a positive preference ('Prefer this over tt_straddle_live / tt_straddle_decay for anything chart-shaped') and a when-not ('Use tt_straddle_decay when the question is about the PATTERN across many sessions').

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