Skip to main content
Glama
Sign In
TradingView Unified MCP

TradingView Unified MCP

by daviddme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_navigate

Navigate a specific Chrome tab to a saved TradingView chart URL and confirm the destination layout ID, blocking navigation away from unsaved changes.

Instructions

Navigate this exact chart tab to a saved TradingView chart URL and verify the destination widget ID. Refuses navigation away from an observed dirty chart.

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": {
      "url": "<url>",
      "target_id": "<target_id>",
      "expected_layout_id": "<expected_layout_id>"
    },
    "name": "browser_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
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

A4.2/5.0
Behavior4/5

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

Annotations declare openWorld=true, non-idempotent, non-destructive, non-readonly, so the description doesn't need to restate safety. It adds real behavioral context beyond them: the dirty-chart refusal guard and the post-navigation widget-ID verification, telling the agent the call can hard-fail rather than silently redirect.

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 tight sentences with zero waste; the action and its scope come first, the failure guard second. Every sentence earns its place.

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?

No output schema exists, and the description mentions the verification of the destination widget ID, giving the agent a sense of what confirms success. It could say more about what happens on a dirty-chart refusal (error vs. no-op) but is largely complete for a 3-param navigation tool.

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% and target_id/expected_layout_id are well described there. The description frames the URL as a saved chart URL and implies expected_layout_id gates the write (mismatch stops), but the raw 'url' parameter itself has an empty schema description and the description adds no format or constraint detail beyond the schema's own fields. Baseline 3.

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+resource ('Navigate this exact chart tab to a saved TradingView chart URL') plus the verification step (destination widget ID). An agent can tell this apart from browser_open_tab or layout_open, which create/open rather than navigate an existing tab to a saved chart URL.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear usage context ('this exact chart tab', 'saved TradingView chart URL') and an explicit precondition/guard: it refuses to navigate away from an observed dirty chart. It does not name the sibling alternatives (browser_open_tab, layout_open) that an agent might confuse it with, so it stops short of full when/when-not routing.

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