Skip to main content
Glama
Sign In
TradingView Unified MCP

TradingView Unified MCP

by daviddme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

study_template_apply

Destructive

Apply one native saved or supplied study template, back up the prior studies, and verify identities plus exposed settings. Replaces active-chart studies.

Instructions

Apply one native saved or supplied study template, back up the prior studies, and verify identities plus exposed settings. Replaces active-chart studies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target_id": "<target_id>",
      "expected_layout_id": "<expected_layout_id>"
    },
    "name": "study_template_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateNo
target_idYesExact Chrome tab target ID from browser_list_tabs. Required for changes.
timeout_msNo
template_idNo
expected_layout_idYesExpected saved-layout ID. A mismatch stops the operation before writing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the destructiveHint annotation, the description discloses that prior studies are backed up, identities and exposed settings are verified, and active-chart studies are replaced. It does not explain where the backup lives, whether it can be restored, or what verification means in practice, so it stops short of full transparency.

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 front-loaded sentences with no filler. The core action comes first and the replacement warning follows, so every sentence 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?

There is no output schema, and the description does not say what verification returns, where the backup is stored, or how partial failures are handled. It gives the essential destructive-effect warning, but leaves meaningful gaps for a nested, open-world mutation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40% across five parameters, including a nested template object, and the description never names template_id versus template, timeout_ms, or the panes array. 'Saved or supplied' hints at the two template input forms but does not compensate for the undocumented parameters.

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?

States a specific verb and resource: apply a native saved or supplied study template, with the effect of replacing active-chart studies. This clearly distinguishes it from study_template_save, study_template_get, and study_template_delete.

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 it by saying it applies a template and replaces active-chart studies, but it names no alternatives such as layout_open or pane_set_layout and gives no prerequisites like saving or supplying a template first. The replacement effect is useful context, but explicit when/when-not guidance is missing.

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