Skip to main content
Glama
gagahkharismanuary

tradingview-mcp-codex

tvx_set_symbol

Change the symbol displayed on a TradingView chart to the specified ticker or exchange-prefixed symbol.

Instructions

Set TradingView chart symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesSymbol or exchange-prefixed symbol
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It fails to disclose what 'set' entails (e.g., changes current chart symbol, requires open chart, persistence). Behavioral traits are minimally conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one short sentence with no wasted words. It front-loads the core function, though more detail could be added without sacrificing conciseness.

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

Completeness2/5

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

For a tool with no annotations and one parameter, the description is under-specified. It lacks information on prerequisites, side effects, or return values, leaving significant gaps in contextual understanding.

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 description coverage is 100% for the single 'symbol' parameter. The description adds no extra meaning beyond the schema, which already describes the parameter format. Baseline score of 3 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?

The description 'Set TradingView chart symbol' clearly states the tool's action and resource. It distinguishes from sibling tools like tvx_chart_state (get state) and tvx_set_timeframe (set timeframe) by focusing on symbol setting.

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. Sibling tools exist but are not mentioned. The description does not specify prerequisites or context for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gagahkharismanuary/tradingview-mcp-codex'

If you have feedback or need assistance with the MCP directory API, please join our Discord server