Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by moeuu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Open local chart viewer

chart_open
Read-onlyIdempotent

Get the local TradingView Lightweight Charts viewer URL to display chart updates made by other tools.

Instructions

Return the local TradingView Lightweight Charts viewer URL. The viewer reflects chart changes made by other tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chart_open"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations are strong: readOnlyHint=true, openWorldHint=false, idempotentHint=true, destructiveHint=false. The description adds context that the tool reflects chart changes, which is useful, but annotations already cover the safety profile.

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?

One concise sentence, no filler, perfectly scoped to the tool's single responsibility.

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 zero-parameter getter with output schema and solid annotations, description is complete. It doesn't specify what happens if viewer is unavailable, but that's out of scope.

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

Parameters4/5

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

Zero params, schema fully covers it; no additional param explanation needed.

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?

Description uses a specific verb (Return) and resource (local TradingView Lightweight Charts viewer URL) and states that the viewer reflects chart changes made by other tools. It doesn't name alternative sibling functions, but the operation is clear enough to route correctly.

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 implied use case is to retrieve the viewer URL after chart mutations. It lacks explicit when-to-use vs alternatives guidance, but mentions its role relative to other tools.

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