TradingView OpenCode Agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CDP_HOST | No | Host de Chrome (default: localhost) | localhost |
| CDP_PORT | No | Puerto de debug de Chrome (default: 9222) | 9222 |
| TIMEOUT_MS | No | Timeout de operaciones (default: 30000ms) | 30000 |
| SCREENSHOT_DIR | No | Directorio para screenshots (default: ./screenshots) | ./screenshots |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tv_health_checkA | Verify CDP connection to TradingView/Chrome |
| tv_launchC | Detect and launch TradingView application |
| chart_get_stateB | Get current chart state: symbol, timeframe, indicators |
| quote_getA | Get current quote (price, OHLC) for a symbol |
| data_get_ohlcvB | Get historical OHLCV bars |
| data_get_study_valuesB | Get values from indicators/studies on chart |
| data_get_pine_linesB | Get drawn lines from Pine scripts |
| data_get_pine_labelsB | Get drawn labels from Pine scripts |
| data_get_pine_tablesB | Get table data from Pine scripts |
| draw_shapeC | Draw a shape on the chart |
| draw_listB | List all drawn objects on chart |
| draw_removeB | Remove a drawn object by ID |
| draw_clearB | Clear all drawings or drawings of a type |
| alert_listB | List all alerts |
| alert_createC | Create a new alert |
| alert_deleteB | Delete an alert by ID |
| capture_screenshotC | Capture chart screenshot |
| replay_startC | Start replay mode |
| replay_stepA | Advance replay by one bar |
| replay_statusB | Get current replay status |
| replay_stopA | Stop replay mode |
| batch_runC | Execute operations across multiple symbols |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Each tool has a clearly distinct purpose, targeting specific actions like data retrieval, drawing, or replay. Overlaps are minimal and descriptions clarify differences, e.g., quote_get vs data_get_ohlcv or study vs pine objects.
Most tools follow a domain_verb_object pattern (e.g., chart_get_state, alert_create), but batch_run and tv_launch deviate slightly in structure. Overall consistent within each subdomain.
With 22 tools, the set is on the heavier side, bordering on excessive for a charting assistant. While each tool serves a distinct function, the overall count could be streamlined without losing core capabilities.
The tool set covers major areas like data, drawings, alerts, and replay, but lacks essential chart modification tools (e.g., set symbol/timeframe, add/remove indicators). This limits the agent's ability to perform full chart interactions.