Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by madiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

tv_launch

Launch TradingView Desktop with Chrome DevTools Protocol remote debugging enabled so AI clients can inspect and control local charts; auto-detects installs on macOS, Windows, and Linux.

Instructions

Launch TradingView Desktop with Chrome DevTools Protocol (remote debugging) enabled. Auto-detects install location on Mac, Windows, and Linux.

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

Input Schema

NameRequiredDescriptionDefault
portNoCDP port (default 9222)
kill_existingNoKill existing TradingView instances first (default false; set true only when a restart is intended)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden and does add real value: it discloses that the process is started with remote debugging enabled and that the install path is auto-detected across three platforms. However, it does not say whether the call blocks until the app is ready, what it returns (PID, confirmed port, nothing), or whether relaunching an already-running instance is a no-op.

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?

Two sentences, zero filler, and the core action with its key behavioral trait (CDP enabled) is front-loaded before the platform support note. Nothing could be removed without loss.

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?

The tool is simple (two optional params, no nested objects) and the description covers what it does and where it works. Since there is no output schema, the description should still indicate what a successful launch yields or how the agent confirms readiness; that gap keeps it at merely adequate.

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%, and the schema already documents both 'port' (default 9222) and 'kill_existing' (default false, restart-only). The description adds no parameter semantics beyond that, so the baseline 3 for a fully documented schema is appropriate.

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 and resource ('Launch TradingView Desktop') and adds the distinguishing detail that CDP remote debugging is enabled. The second sentence adds cross-platform auto-detection. It is clearly distinct from inspection siblings like tv_health_check or tv_discover, though the description never names those alternatives to reinforce the contrast.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers it should call this when the desktop app is not running and CDP access is needed. There is no explicit statement of when to use this versus tv_discover or tv_health_check, and no guidance on prerequisites such as whether TradingView must be installed or already authenticated.

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