TradingView-MCP

Overview Schema Source Related Servers Discussions Admin

get_trade_decision_context

Compile a read-only trade-analysis evidence bundle from chart, OHLCV, key levels, scanner quotes, events, COT, real yield, and bid/ask data, reporting data readiness without making directional recommendations.

Instructions

Build one read-only evidence bundle for trade analysis from a symbol-bound TradingView chart, OHLCV, key levels, scanner MTF/quotes, events, COT, U.S. real yield, and bid/ask execution evidence. decision_status reports only data and gate readiness; it never produces a directional recommendation or changes charts, Pine, alerts, orders, or journals.

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": {
      "symbol": "<symbol>",
      "expected_timeframe": "<expected_timeframe>"
    },
    "name": "get_trade_decision_context"
  }
}

Input Schema

Name	Required	Description	Default
`fields`	No
`symbol`	Yes
`countries`	No
`timeframes`	No
`chart_index`	No
`ohlcv_count`	No
`min_importance`	No
`key_level_limit`	No
`auxiliary_symbols`	No
`expected_timeframe`	Yes
`include_real_yield`	No
`require_real_yield`	No
`include_positioning`	No
`require_positioning`	No
`key_level_range_percent`	No
`minimum_event_importance`	No
`execution_max_quote_age_ms`	No
`event_blackout_after_minutes`	No
`execution_sample_interval_ms`	No
`execution_wait_for_update_ms`	No
`event_blackout_before_minutes`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.10Sep 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states the tool is read-only, never recommends a direction, and does not mutate charts, Pine, alerts, orders, or journals. It also clarifies that decision_status reports only data and gate readiness, which is valuable beyond the schema. It omits potential failure modes or latency, but the core side-effect profile is well disclosed.

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?

The description is two sentences with no filler. The first sentence front-loads the core purpose and scope, and the second adds essential safety semantics. Every phrase earns its place.

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

Completeness2/5

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

This is a high-complexity tool with 21 parameters, no output schema, and no annotations. The description gives a useful high-level overview and safety guarantees, but omits the return structure, how parameters shape the bundle, what 'gate readiness' means concretely, and how to handle failures or partial data. An agent would need significant additional inference to invoke this tool confidently for varied use cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are 21 parameters and the schema description coverage is 0%, yet the description only lists high-level data domains (OHLCV, key levels, events, COT, real yield, execution evidence). It does not explain critical parameters like expected_timeframe vs. timeframes, include_real_yield vs. require_real_yield, event blackout windows, or execution timing controls. The description cannot compensate for the complete absence of parameter-level guidance.

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 opens with a specific verb and resource: 'Build one read-only evidence bundle for trade analysis.' It enumerates the data sources included and explicitly states what it never does, which distinguishes it from mutation-oriented siblings and single-source getters.

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 clearly implies when to use it: when a consolidated, multi-source evidence bundle for trade analysis is needed. It also establishes exclusions by stating that it never produces a directional recommendation and never changes charts, Pine, alerts, orders, or journals, though it does not name specific alternative tools.

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

Deploy Server