TradingView MCP

Overview Schema Source Related Servers Discussions Admin

Analyze current chart

chart_analyze

Read-onlyIdempotent

Calculate deterministic trend, moving averages, RSI, MACD, Bollinger Bands, ATR, signals, and support/resistance from current bars.

Instructions

Calculate deterministic trend, SMA/EMA, RSI, MACD, Bollinger Bands, ATR, signals, and support/resistance from the current bars. This is not investment advice.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 20, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) already convey the safety profile. The description adds the trait 'deterministic', which is useful behavioral context, and lists exact computations (SMA/EMA, RSI, etc.). The disclaimer about investment advice, while not a behavior, is extra context. No contradiction exists.

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 a single, well-structured sentence of what it computes, followed by a brief disclaimer. No superfluous words, and the most important action ('calculate' + indicator list) is front-loaded.

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?

Given zero parameters, no output schema, and a clear 'current chart' context, the description provides a reasonable enumeration of all the indicator families it returns, which is fairly complete. However, it could mention the output format or any side-context like the chart needing to be open (implied by 'current bars') but that is minor. The completeness is adequate for an analysis tool.

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?

The tool has zero parameters, so baseline is 4 per guidelines. The description clarifies it operates on 'current bars' and lists the calculated indicators, which is helpful beyond the empty schema. No parameter-specific details are needed.

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 uses a specific verb 'calculate' and a clear resource 'current chart' with a detailed list of indicators (trend, SMA/EMA, RSI, MACD, etc.). It clearly distinguishes from siblings like tradingview_analyze_symbol by focusing on the current chart, and no ambiguity is present.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives is provided. The description only states what it does and disclaims investment advice, but does not mention when it should be preferred over sibling tools like tradingview_analyze_symbol or chart_get_state. The 'current chart' context is implied but not explicitly compared.

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