TradingView-MCP

Overview Schema Source Related Servers Discussions Admin

run_yield_price_nonconfirmation_study

Detect cross-asset nonconfirmation events where a target fails to break as expected after a driver impulse, then measure forward returns, MFE, MAE, target timing, and fold results.

Instructions

Run a bounded, read-only cross-asset event study over two exact TradingView charts, with an optional third-chart OHLC regime or fixed DXY Pine gate on the target chart. A driver impulse becomes usable only after its nominal bar close; the study then tests whether the target fails to break in the expected direction and confirms an opposite structural close. It uses an as-of join without forward-fill and returns forward return, MFE, MAE, target timing, fold results, and explicit exclusions. Signal-bar close is an event reference, not an assumed fill. It never changes charts, ranks parameters, or places orders.

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": {
      "target_chart_index": "<target_chart_index>",
      "driver_chart_index": "<driver_chart_index>",
      "expected_target_symbol": "<expected_target_symbol>",
      "expected_driver_symbol": "<expected_driver_symbol>",
      "expected_target_timeframe": "<expected_target_timeframe>",
      "expected_driver_timeframe": "<expected_driver_timeframe>",
      "relationship": "<relationship>",
      "driver_lookback": "<driver_lookback>",
      "driver_change_threshold": "<driver_change_threshold>",
      "price_breakout_lookback": "<price_breakout_lookback>",
      "nonconfirmation_bars": "<nonconfirmation_bars>",
      "trigger_lookback": "<trigger_lookback>",
      "trigger_within_bars": "<trigger_within_bars>",
      "max_driver_age_bars": "<max_driver_age_bars>",
      "horizons": "<horizons>",
      "target_return_bps": "<target_return_bps>",
      "minimum_events": "<minimum_events>"
    },
    "name": "run_yield_price_nonconfirmation_study"
  }
}

Input Schema

Name	Required	Description
`count`	No	Most recent loaded bars to inspect on each chart. Default: 5000
`folds`	No
`horizons`	Yes	Observed-bar return horizons. Only horizon 1 can be statistically candidate-eligible.
`event_limit`	No	Maximum per-event rows to return. Aggregate metrics always use all events. Default: 50
`signal_from`	No	Inclusive signal-bar timestamp for a fixed forward collection window
`relationship`	Yes
`context_regime`	No
`minimum_events`	Yes
`driver_lag_bars`	No	Lag offset in target bars after driver impulse close (default: 0)
`driver_lookback`	Yes
`trigger_lookback`	Yes
`context_indicator`	No
`target_return_bps`	Yes
`driver_chart_index`	Yes
`target_chart_index`	Yes
`max_driver_age_bars`	Yes
`trigger_within_bars`	Yes
`configuration_trials`	No	Number of evaluated lead/lag and parameter trials for multiple testing reference (default: 1)
`nonconfirmation_bars`	Yes
`expected_driver_symbol`	Yes
`expected_target_symbol`	Yes
`driver_change_threshold`	Yes
`price_breakout_lookback`	Yes
`expected_driver_timeframe`	Yes
`expected_target_timeframe`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.10Sep 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so exceptionally. It explicitly discloses read-only behavior, bounded execution, as-of join without forward-fill, no assumed fill at signal-bar close, explicit exclusions, and states it never changes charts, ranks parameters, or places orders.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences with no filler. The opening sentence front-loads the core purpose and safety profile, and each subsequent sentence adds distinct value: event logic, join and output semantics, fill reference, and side-effect guarantees.

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?

Given the high complexity (25 parameters, no output schema, no annotations), the description is unusually complete. It explains the study mechanics, the optional gate variants, the join behavior, the returned metrics, and the tool's non-mutating guarantees, giving an agent enough context to invoke it appropriately.

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 only 24%, and no output schema is present, so the description must compensate. It supplies essential semantics for many required parameters by defining the driver impulse, signal-bar close timing, as-of join behavior, optional third-chart gate, and the output metrics. It does not enumerate every parameter, but the conceptual model it provides is substantial.

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?

The description states a specific verb and resource: "Run a bounded, read-only cross-asset event study over two exact TradingView charts." It further distinguishes itself by naming the nonconfirmation logic, optional DXY gate, and the fact that it is a study rather than a chart-mutating action, which separates it from the many sibling event-study tools.

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

Usage Guidelines4/5

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

The description provides clear context for when this tool is appropriate: when analyzing a driver impulse against a target nonconfirmation with an optional regime gate. It does not name sibling tools or explicitly state when not to use it, but the event pattern and read-only bounded study framing give an agent enough context to select it over unrelated tools.

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

Deploy Server