Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

set_visible_range

Scrolls and zooms the TradingView chart to a specified time range using Unix timestamps, so you can focus on exact market periods.

Instructions

Scroll and zoom the chart to a time range (unix seconds).

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": "set_visible_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose that this is a pure viewport manipulation (scroll/zoom of the chart) rather than a data mutation, plus the unit convention. It does not say what happens if the range falls outside available data, whether existing zoom is replaced, or whether the change persists.

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?

A single tight sentence that front-loads the action and ends with the critical unit clarification. No filler or redundancy.

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 two-parameter viewport tool with no output schema, the core information an agent needs is present. Missing edge-case behavior (out-of-range values, effect on existing zoom) keeps it from being fully 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 0%, so the description must compensate; it does the most important thing by declaring the unit "unix seconds" for the range. It adds nothing about whether from must precede to, whether bounds are inclusive, or acceptable ranges, leaving the two numeric params partly underspecified.

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 specific verb pair ("scroll and zoom") and resource ("the chart") plus the target state ("a time range"), so an agent knows exactly what the tool changes. It does not distinguish itself from view-related siblings, but the action itself is unambiguous.

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 call this versus other chart-state tools, nor any prerequisites or exclusions. The agent must infer that this is for focusing the viewport rather than querying data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.