Skip to main content
Glama

Preview An Idea (Free)

tt_preview_idea
Read-onlyIdempotent

Free, read-only preview of a single-stock daily idea: "what if I bought X whenever Y, and sold it Z later?" for NSE stocks/ETFs. Creates nothing, charges nothing, needs no sign-in.

Returns a daily PREVIEW replay — trades, win rate, net return vs buy-and-hold, recent trades, data-quality notes — plus the validated strategy it would run. Report it with its limits: it is not the backtest engine. EXIT IS REQUIRED AND HAS NO DEFAULT: if the user did not say when to sell, ask. The window defaults to the 3 years ending 35 days before today (data at least 35 days old, exchange rule).

A real engine backtest of the same idea is tt_backtest_idea with run_backtest=true — paid, and it asks the price first. Offer it; call it only when the user asks for it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tt_preview_idea"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
exitNoOptional exit rules (same grammar), ORed with hold_days.
entryNoEntry rules on DAILY candles, comma-separated, ANDed — same grammar as tt_backtest_idea, e.g. 'rsi(14) < 30'.
startNo
symbolNoNSE stock or ETF trading symbol, e.g. RELIANCE, SBIN, NIFTYBEES. Indices cannot be bought in cash — use an index ETF.
quantityNoShares per trade. Scales rupee figures only.
hold_daysNoSell this many CALENDAR days after entry. 0 = no time exit (then `exit` is required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real value: no charge, no sign-in, nothing created, the 35-day data-age exchange rule behind the default window, and the warning to report results alongside their `limits` because this is not the backtest engine. The only gap is that it doesn't mention latency or result-size/pagination behavior.

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-loaded with what it is and what it costs before the constraints and the alternative. Slightly verbose — 'Creates nothing, charges nothing, needs no sign-in' restates the read-only annotation, and the reported-return list plus the limits caveat could be tightened.

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

Completeness5/5

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

No output schema exists, so the description carries the return-value burden and does: trades, win rate, net return vs buy-and-hold, recent trades, data-quality notes, plus the validated strategy it would run. Combined with the exit requirement and default window, an agent has everything needed to call and report this correctly.

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?

Schema coverage is 71%, and the description compensates for the undocumented `start`/`end` by explaining the default window (3 years ending 35 days before today). It reinforces the exit-vs-hold_days relationship, though that is largely repeated from the schema, and says nothing extra about `quantity` beyond the schema's own note.

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 and resource — a free, read-only preview replay of a single-stock daily entry/exit idea for NSE stocks/ETFs — and immediately frames it as the 'what if I bought X whenever Y, sold later' question. It explicitly distinguishes itself from tt_backtest_idea, so the agent can route without opening either schema.

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 when-to-use and when-not-to-use: offer the paid tt_backtest_idea but call it only when the user asks. It also states a hard prerequisite — EXIT IS REQUIRED AND HAS NO DEFAULT, ask the user if they didn't say when to sell — which is exactly the kind of pre-call behavior an agent needs.

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