Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by moeuu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Close TradingView Supercharts browser

tradingview_close

Close the managed TradingView browser session, preserving local authentication files.

Instructions

Close the managed TradingView browser, context, and page. Authentication files remain local and untouched.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate this is not read-only, not idempotent, and not destructive. The description adds value by specifying exactly what is closed (browser, context, page) and reassuring that 'Authentication files remain local and untouched.' This is useful behavioral context beyond the structured annotations.

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. The first states the core action and scope; the second adds a key safety clarification. Every word earns its place with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter close operation with no output schema, the description is complete: it names the exact resources affected and clarifies that authentication files are preserved. No additional context is necessary for correct invocation.

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?

The tool has zero parameters and the schema confirms this with an empty properties object. Description adds nothing about parameters because none exist, so the baseline of 4 applies.

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 uses a specific verb, 'Close', and identifies the exact resources: 'managed TradingView browser, context, and page.' This clearly distinguishes the tool from sibling tools like tradingview_open_chart or chart_get_state, none of which perform a close operation.

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?

The description provides clear context: it closes the managed TradingView browser/context/page, implying it is the counterpart to an open/session tool. However, it does not explicitly state when to use it vs. alternatives or mention prerequisites like 'after opening a chart.'

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