Skip to main content
Glama
Sign In
TradingView Unified MCP

TradingView Unified MCP

by daviddme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

alert_create

Create a TradingView alert directly from price thresholds, strategy order fills, or indicator conditions, with idempotency and configuration verification before applying changes.

Instructions

Create a native alert directly, without requiring a template. Supports price thresholds, attached Pine strategy order fills and discovered indicator alertconditions. Durable idempotency plus independent configuration verification; defaults to requesting paused state.

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": {
      "name": "<name>",
      "idempotency_key": "<idempotency_key>",
      "condition": "<condition>",
      "target_id": "<target_id>",
      "expected_layout_id": "<expected_layout_id>"
    },
    "name": "alert_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
activeNo
symbolNo
messageNo
conditionYes
target_idYesExact Chrome tab target ID from browser_list_tabs. Required for changes.
resolutionNo
webhook_urlNo
notificationsNo
message_formatNotext
expiration_daysNo
idempotency_keyYes
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

C2.7/5.0
Behavior1/5

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

Annotations declare idempotentHint=false, while the description advertises 'Durable idempotency'; that is a direct behavioral conflict. Valuable extra context about independent verification and the paused default exists, but the contradiction forces a 1.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences front-load the purpose and capabilities with little waste. The second sentence is slightly overloaded but remains structured and informative.

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

Completeness2/5

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

For a 13-parameter nested create tool with no output schema and low schema coverage, the description omits too many operational details about notifications, expiration, webhook behavior, and condition subfields. It covers purpose and some condition semantics but not enough to confidently invoke across all parameters.

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

Parameters2/5

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

Schema description coverage is only 15% across 13 parameters, so the description must compensate. It maps the condition families and mentions idempotency and verification, but leaves active, symbol, message, resolution, webhook_url, notifications, message_format, expiration_days, and most condition subfields unexplained.

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?

Starts with a specific verb and resource ('Create a native alert directly') and clarifies it does not require a template. It also names supported condition families (price, strategy, indicator), but does not explicitly distinguish itself from siblings like alert_create_bulk or alert_prepare.

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 phrase 'without requiring a template' implies when to use this tool rather than a template-based path, but no alternative sibling is named. There is no explicit when-not guidance or mention of prerequisites such as target_id and expected_layout_id.

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