Skip to main content
Glama
Sign In
TradingView-MCP

TradingView-MCP

by tedorigawa001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

set_symbol

Change the symbol displayed on a TradingView chart, optionally targeting a specific pane in multi-chart layouts. Failed changes roll back to the previous symbol.

Instructions

Change one TradingView chart to a different symbol, e.g. 'BTCUSD', 'OANDA:EURUSD', 'NASDAQ:AAPL'. chart_index selects a pane in multi-chart layouts; the active chart is used by default. The target pane is read back and failures are rolled back.

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>"
    },
    "name": "set_symbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesSymbol to display, optionally exchange-prefixed
chart_indexNoChart index in a multi-chart layout. Default: active chart

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.10

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral transparency burden. It discloses that the target pane is read back and failures are rolled back, which is meaningful for a mutating tool. It does not mention permissions or persistence, but the core side effects are sufficiently transparent for this simple operation.

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?

Three tight sentences with the core action front-loaded, useful examples, and no redundant filler. Every clause contributes either to scope, parameter behavior, or failure handling.

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?

For a two-parameter mutating tool with no output schema, the description is complete: it specifies what changes, acceptable symbol formats, how to target a pane, the default behavior, and the rollback guarantee. Nothing essential is missing for correct invocation.

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 100%, so the baseline is 3, but the description adds value by giving real symbol format examples and clarifying that chart_index selects a pane in multi-chart layouts with the active chart as default. This goes beyond the bare schema text.

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 precise verb and resource: 'Change one TradingView chart to a different symbol.' It gives concrete symbol format examples ('BTCUSD', 'OANDA:EURUSD', 'NASDAQ:AAPL') and is clearly distinct from sibling set_timeframe, which changes a different chart property.

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 explains chart_index usage and the default behavior for the active chart, giving an agent enough context to invoke the tool correctly. It does not explicitly name alternatives or exclusions, but the operation is unambiguous and no competing sibling performs the same symbol-change task.

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

Deploy Server

Other Tools