Skip to main content
Glama
firyomaefx

TradingView Chrome MCP

by firyomaefx

tv_change_timeframe

Destructive

Change the active TradingView chart timeframe to a specified value (1, 5, 15, 30, 60, 240 minutes, daily, weekly, monthly). Directly modifies the user's current chart view.

Instructions

Change the active chart timeframe. DESTRUCTIVE: modifies the user's chart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeframeYesOne of: 1,5,15,30,60,240,D,W,M
Behavior3/5

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

Annotations already include destructiveHint=true. The description adds 'DESTRUCTIVE: modifies the user's chart', which restates the annotation with slight elaboration but no new behavioral details beyond what annotations provide.

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?

Extremely concise with two sentences, no unnecessary words. Front-loaded with the core action, then the destructive warning.

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

Completeness4/5

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

For a simple modification tool with one parameter and annotations covering destructiveness, the description is adequate. It could mention that it affects the currently active chart, but its brevity is acceptable.

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%, and the parameter list is fully documented in the schema. The tool description adds no additional meaning or context beyond the schema.

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?

Description clearly states 'Change the active chart timeframe' with a specific verb and resource. Among the many sibling tools, no other tool changes the timeframe, so it is easily distinguished.

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. There is no mention of context, prerequisites, or conditions 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/firyomaefx/tradingview-chrome-mcp'

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