Skip to main content
Glama
Sign In
TradingView Unified MCP

TradingView Unified MCP

by daviddme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

layout_save

Saves the current TradingView chart layout in place, with optional rename, and verifies the expected layout ID to prevent writing to the wrong layout.

Instructions

Save the current layout in place, optionally renaming it. This is not a duplicate operation.

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": "layout_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
target_idYesExact Chrome tab target ID from browser_list_tabs. Required for changes.
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.5/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, non-idempotent mutation. The description adds useful context that it saves in place and optionally renames, but it does not explain what is overwritten, how expected_layout_id affects safety, or what happens on mismatch beyond what the schema states.

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?

The description is two short sentences with no wasted language, and the core operation is stated first. The second sentence usefully clarifies the non-duplicate behavior.

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?

For a mutation tool with annotations and no output schema, the description covers the basic purpose but leaves out richer behavioral details such as what in-place saving persists or overwrites. The schema carries the concurrency parameter, but the overall description is only minimally 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 67%: target_id and expected_layout_id are documented in the schema. The description adds the meaning of the optional name parameter by saying the layout can be "optionally renaming it," but it does not add details for the required parameters.

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 clearly states a specific verb and resource: save the current layout in place, with optional renaming. It also explicitly says this is not a duplicate operation, which helps distinguish it from layout_copy, though it does not directly distinguish it from layout_rename or layout_create.

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?

It gives one useful exclusion: "not a duplicate operation." However, it does not state when to choose this over layout_rename, layout_create, or layout_copy, so the usage guidance remains implied rather than explicit.

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