Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by madiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

chart_manage_indicator

Add or remove technical indicators and studies on a TradingView chart to adjust analysis.

Instructions

Add or remove an indicator/study on the chart

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": {
      "action": "<action>"
    },
    "name": "chart_manage_indicator"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction: add or remove
inputsNoJSON string of input overrides for the indicator (e.g., '{"length": 20}')
entity_idNoEntity ID (from chart_get_state). Required for remove.
indicatorNoFull indicator name (required for add): "Relative Strength Index", "MACD", "Volume", "Moving Average", "Bollinger Bands", "Moving Average Exponential". Short names like RSI/EMA do NOT work. Not needed for remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only names the actions (add/remove) without revealing side effects, requirements (e.g., chart must be loaded), error behavior, or impact on existing indicators. This is insufficient for a mutation tool.

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?

The description is a single, crisp sentence that front-loads the core action and resource. It is appropriately concise and wastes no words, though it could be slightly more structured to mention the conditional parameter usage.

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 tool has 4 parameters (one with a JSON string, one with an enum) and no output schema, the description is far too thin. It does not explain what happens after a successful add/remove, whether the operation is idempotent, or how the inputs field interrelates with the action. An agent would need to infer critical details from the schema alone.

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 all parameters are individually described, including the enum for action and the conditional requirements for entity_id and indicator. The description itself adds no extra context beyond what the schema already provides, so it stays at the baseline expected for full schema coverage.

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 clear verb ('Add or remove') and a specific resource ('indicator/study on the chart'), making the core purpose unambiguous. However, it does not explicitly distinguish itself from the sibling tool 'indicator_add', which likely performs a similar add operation, so it misses the opportunity to avoid confusion.

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?

There is no guidance on when to use this tool versus alternatives like indicator_add, indicator_remove, or indicator_toggle_visibility. The schema hints that entity_id is needed for remove and indicator is needed for add, but the description itself provides no context on selection criteria or prerequisites.

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