Skip to main content
Glama

get_ai_quant_candle_packet

Compute zero-repaint, closed-bar candle analytics and deterministic ATR risk packets with EMA regime, ADR fuel, and stop/target sizing across stocks, crypto, commodities, and FX.

Instructions

Compute a zero-repaint (closed-bar only) quantitative analysis & deterministic ATR risk packet. [日本語検索キーワード: 確定足リスクマップ / 損切り・利確ライン / ATR / ADR値幅燃料 / EMAトレンド判定]

Supported timeframes: '5m', '15m', '30m', '1h', '1d'. Works across US Stocks ('NVDA', 'AAPL'), Japanese Stocks ('7203.T', '8035.T'), Crypto ('BTC-USD', 'SOL-USD'), Commodities ('GLD', 'XAUUSD'), and FX ('USDJPY').

Returns:

  • Confirmed closed candle OHLCV (eliminates mid-candle repainting)

  • EMA(20/50/200) alignment + Weinstein 200-Day SMA Stage-2 regime

  • Causal 15-day ADR% & remaining intraday ADR fuel% (chasing-exhaustion warning)

  • Schmitt-Trigger Factor Ontology semantic polarity tags (prevents LLM polarity hallucinations)

  • Deterministic 1.5x ATR structural stop loss, 1.5R partial & 3.0R runner targets, and unit sizing per $100 risk.

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": "get_ai_quant_candle_packet"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoNVDA
timeframeNo1h

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does so well: it states the zero-repaint/closed-bar guarantee, names deterministic 1.5x ATR stop placement, and warns that ADR fuel% signals chasing exhaustion. It omits operational traits such as authentication requirements, rate limits, or latency expectations, which keeps it short of a 5 for an unannotated tool.

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?

The purpose statement is front-loaded and the 'Returns' bullet list is genuinely useful structure. Against that, the Japanese keyword line and dense jargon ('Schmitt-Trigger Factor Ontology semantic polarity tags') consume space without helping an agent select or invoke the tool, so the description is denser than it needs to be.

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 an output schema present, the description did not need to detail return values, yet its summary of the packet contents is a reasonable aid. For a two-parameter compute tool, the definition covers applicability, valid inputs, and output shape; only operational details (permissions, limits, latency) are missing.

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 description coverage is 0%, so the description must supply meaning, and it does: timeframe literals are enumerated exactly, and the symbol parameter is illustrated with concrete formats across five asset classes ('NVDA', '7203.T', 'BTC-USD', 'XAUUSD', 'USDJPY'). It never explicitly labels these as the symbol and timeframe inputs, and defaults are left to the schema, so it falls just short of full compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and artifact: 'Compute a zero-repaint (closed-bar only) quantitative analysis & deterministic ATR risk packet.' That is far more than a restatement of the name, and the enumerated outputs (EMA alignment, ADR fuel%, ATR stops) make the tool's scope unambiguous. It does not explicitly distinguish itself from siblings like get_live_l2_orderbook, but the closed-bar/risk-packet framing is distinctive enough that an agent can route correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Guidance is implied rather than stated: the supported timeframe list ('5m','15m','30m','1h','1d') and the asset-class examples (US stocks, JP stocks, crypto, commodities, FX) tell an agent where the tool applies. However, there is no explicit when-to-use/when-not-to-use statement and no named alternative for live/intraday data, so the caller must infer that live orderbook work belongs to a sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.