Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by moeuu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Remove chart price zone

chart_remove_zone

Remove a shaded chart zone by its unique ID to clean up overlays and restore chart clarity.

Instructions

Remove a shaded chart zone by id.

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": {
      "id": "<id>"
    },
    "name": "chart_remove_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior1/5

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

The description says 'Remove', which is a destructive action, but the annotations declare destructiveHint: false, meaning the operation is not considered destructive. This directly contradicts the description. The description also does not disclose any other behavioral traits (e.g., what happens if the id doesn't exist).

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 a single, concise sentence that is front-loaded with the action and target. There is zero extraneous information, making it highly efficient.

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 simple deletion tool, the description omits crucial context: no mention of error behavior, id requirements beyond schema, or interaction with other zone operations. The annotation contradiction further reduces completeness, as the agent cannot reliably infer the operation's safety profile.

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?

The only parameter is 'id', and the description literally says 'by id', which adds minimal semantic value beyond the schema's type and constraints. Since schema description coverage is 0%, the description does not explain the id format or purpose beyond the obvious reference, so it falls short of compensating.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Remove a shaded chart zone by id' clearly states the action (remove), the resource (shaded chart zone), and the identifier (by id). It distinguishes from sibling tools like chart_remove_level and chart_remove_marker, which target different chart elements.

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 description implies usage (when you want to remove a zone by its id) but provides no explicit context about when not to use it or alternatives. While the sibling list suggests other removal tools, no exclusions are mentioned, so the guidance is implicit rather than explicit.

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