Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by madiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

chart_set_visible_range

Zooms a TradingView chart to a specific date range using Unix timestamps, so you can focus analysis on exact start and end dates.

Instructions

Zoom the chart to a specific date range (unix timestamps)

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "chart_set_visible_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd of range (unix timestamp in seconds)
fromYesStart of range (unix timestamp in seconds)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 mentions zooming but does not explain whether the existing visible range is replaced, whether a chart must already be loaded, how invalid ranges (from > to) are handled, or whether the change is reversible.

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, front-loaded sentence with no filler. It conveys the action, the target, and the relevant unit context efficiently.

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 simple two-parameter setter, the description plus schema is sufficient to understand the basic call. However, the absence of annotations and the lack of behavioral or usage context leave gaps around prerequisites and side effects, so it is only minimally complete.

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%, with both 'from' and 'to' already described as unix timestamps in seconds and start/end of range. The description adds the phrase 'specific date range' but no additional semantic detail beyond what the schema provides, so baseline 3 is appropriate.

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 states a specific verb ('Zoom') and resource ('the chart') and clearly indicates the action is setting the visible date range. This distinguishes it from sibling tools like chart_get_visible_range (read) and chart_scroll_to_date (navigation).

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 is given about when to use this tool versus alternatives such as chart_scroll_to_date or chart_get_visible_range. There are no prerequisites, exclusions, or context clues beyond the implicit meaning of the description.

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