Skip to main content
Glama
Sign In
TradingView Unified MCP

TradingView Unified MCP

by daviddme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

alert_update

Update a TradingView alert's name, message, webhook, or notifications; reactivate a paused alert only if explicitly allowed, and report every unverified field.

Instructions

Update name, message, webhook or notifications through the native alert model. Refuses to re-arm a paused alert unless explicitly allowed; reports every unverified field.

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": {
      "alert_id": "<alert_id>",
      "patch": "<patch>",
      "target_id": "<target_id>",
      "expected_layout_id": "<expected_layout_id>"
    },
    "name": "alert_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYes
alert_idYes
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.
allow_temporary_activationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Goes meaningfully beyond annotations: it discloses the re-arm guard ('refuses to re-arm a paused alert unless explicitly allowed'), which explains the allow_temporary_activation parameter, and the reporting behavior ('reports every unverified field'), which hints at partial-verification outcomes. It does not discuss atomicity or what happens to fields omitted from the patch, so it stops short of 5.

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 tight sentences, front-loaded with the operation and followed by the guard condition; every clause carries information. 'Through the native alert model' is the one soft phrase that adds little for an agent.

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 non-idempotent mutation with a nested patch object, 4 required params, 40% schema coverage and no output schema, the description covers the patch surface and the re-arm guard but omits whether updates are atomic, how omitted fields are treated, and what 'unverified field' reporting actually returns.

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 only 40%, with descriptions on target_id and expected_layout_id but nothing on alert_id, patch.active, or allow_temporary_activation. The description does map most of the patch sub-fields and implicitly explains the re-arm flag, but leaves `active` and `message_format` semantics and the alert_id format 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?

States a concrete verb+resource (update an alert) and enumerates the mutable fields (name, message, webhook, notifications), which lets an agent tell it apart from alert_pause/alert_resume/alert_delete. It does not explicitly say 'use alert_update for field edits, not alert_pause for active state,' so sibling differentiation is only implied.

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?

Usage is implied: this is the field-editing path, while activation state has dedicated siblings. However there is no explicit when-to-use/when-not statement, and the presence of `active` inside `patch` alongside the dedicated alert_pause/alert_resume tools leaves a real ambiguity the description never resolves.

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