Skip to main content
Glama
firyomaefx

TradingView Chrome MCP

by firyomaefx

tv_layout_duplicate

Destructive

Duplicate the current TradingView chart layout and optionally rename the copy to create a new layout in your account.

Instructions

Duplicate the active chart layout. Optionally provide a new name. DESTRUCTIVE: creates a new layout in your account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional name for the duplicated layout
Behavior5/5

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

The description explicitly states 'DESTRUCTIVE: creates a new layout in your account', which adds behavioral context beyond the destructiveHint annotation. It warns about side effects (creating new layout) that may affect account limits or layout clutter.

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 short sentences with no filler. The first sentence states the core action, the second adds optionality and destructiveness. Every word earns its place.

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 description covers the action and side effect, but lacks detail on return value (e.g., layout ID), behavior when no active layout exists, and whether the copy becomes active. For a simple tool with one optional param, it is adequate but not fully complete.

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 the description adds little new information. It restates the optional name parameter as 'Optionally provide a new name', which is slightly clearer but not significantly enriching beyond schema's 'Optional name for the duplicated layout'.

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?

The description clearly states the action: 'Duplicate the active chart layout'. The verb 'Duplicate' and resource 'active chart layout' are specific. It also mentions optional naming, which distinguishes it from sibling tools like tv_layout_rename (rename) and tv_layout_save (save).

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?

The description implies when to use (to create a copy of the active layout) but does not explicitly state when not to use or provide alternatives. The optional naming is mentioned, but no guidance on competing tools is given.

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