Skip to main content
Glama
Sign In
TradingView OpenCode Agent

TradingView OpenCode Agent

by jadatorin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

alert_create

Set up a TradingView alert using a custom Pine Script condition, symbol, interval, and message to receive notifications when specific technical patterns occur.

Instructions

Create a new alert

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

Input Schema

NameRequiredDescriptionDefault
symbolNoTradingView symbol
messageNoAlert message text
intervalNoChart interval
conditionYesAlert condition (e.g., "crossover(ta.sma(close,20), ta.sma(close,50))")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states 'create', omitting side effects (e.g., does the alert trigger immediately? are there limits?), making it insufficient for safe invocation.

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

Conciseness2/5

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

The description is a single sentence but under-specified. While concise, it fails to deliver useful information beyond the tool name, thus not earning its place.

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?

Given the complexity of creating alerts (multiple parameters, no output schema), the description is incomplete. It does not mention return values, validation, or how the alert behaves after creation, leaving significant gaps.

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 baseline is 3. The description adds no meaning beyond the schema; it does not explain how parameters interact or provide examples. Baseline score is appropriate.

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 clearly states the verb 'create' and resource 'alert', making it obvious what the tool does. However, it does not differentiate from sibling tools like 'alert_list' or 'alert_delete', missing an opportunity to clarify its unique role.

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 on when to use this tool versus alternatives (e.g., batch_run for multiple alerts). Lacks prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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