Skip to main content
Glama
Sign In
TradingView Unified MCP

TradingView Unified MCP

by daviddme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

chart_set_symbol

Set a full exchange:symbol on a TradingView chart tab and verify the chart label and resolved main-series instrument, blocking writes when the layout ID mismatches.

Instructions

Set a full exchange:symbol and verify both the chart label and resolved main-series instrument identity.

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>",
      "target_id": "<target_id>",
      "expected_layout_id": "<expected_layout_id>"
    },
    "name": "chart_set_symbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesFull exchange:symbol
target_idYesExact Chrome tab target ID from browser_list_tabs. Required for changes.
expected_layout_idYesExpected saved-layout ID. A mismatch stops the operation before writing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, non-idempotent, open-world mutation, and the description adds that it verifies both the chart label and the resolved main-series instrument identity – meaningful behavioral context beyond the annotations. It stops short of describing failure modes or what a failed verification looks like.

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?

A single front-loaded sentence with no filler; the write action and the verification behavior are both stated up front.

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

Completeness3/5

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

For a 3-parameter mutation with no output schema, the definition is mostly sufficient because the schema carries the parameter detail. However, since no output schema exists, the description should say how the verification outcome is reported, and it doesn't.

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

Parameters3/5

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

Schema coverage is 100%, so all three parameters (including the guard-rail expected_layout_id and target_id) are already documented in the schema. The description only echoes the symbol parameter's 'exchange:symbol' format and adds no new semantics for the other two.

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?

States a specific verb ('Set') and resource ('full exchange:symbol') plus a verification step, so the agent knows it writes the chart's symbol and checks the result. It doesn't explicitly contrast with sibling pane_set_symbol, so it falls short of a 5.

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?

There is no explicit when/when-not guidance and no mention of alternatives such as pane_set_symbol or chart_symbol_search. The usage is only inferable from the verb and the parameter names.

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