Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by madiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ui_mouse_click

Clicks exact pixel coordinates in the TradingView window to select chart elements, open menus, or control drawings with left, right, middle, or double-click actions.

Instructions

Click at specific x,y coordinates on the TradingView window

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "ui_mouse_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX coordinate (pixels from left)
yYesY coordinate (pixels from top)
buttonNoMouse button (default left)
double_clickNoDouble click (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention coordinate system details, viewport vs window coordinates, focus requirements, side effects of clicking, or whether the action performs a real OS-level click versus an internal UI event.

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 one efficient sentence with no filler. It front-loads the essential action and target without repetition.

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 simple 4-parameter action, the description is mostly adequate, but it leaves out coordinate-system semantics and relation to ui_click. Given the low tool complexity and complete schema, this is acceptable but not fully self-sufficient.

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 100%, so the schema already documents all four parameters. The description adds minimal semantic value beyond restating that x,y coordinates are used; it does not clarify coordinate origin, units, or interactions between button and double_click.

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 states a specific verb ('Click') and resource ('specific x,y coordinates on the TradingView window'). It is clear, though it does not explicitly distinguish itself from the sibling 'ui_click' tool.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool over alternatives like ui_click or ui_hover. The context implies coordinate-based clicking, but exclusions and alternatives are not stated.

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