Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by madiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

replay_autoplay

Toggle autoplay in TradingView replay mode and optionally set playback delay to control how quickly replay progresses.

Instructions

Toggle autoplay in replay mode, optionally set speed

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "replay_autoplay"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedNoAutoplay delay in ms (lower = faster). Valid values: 100, 143, 200, 300, 1000, 2000, 3000, 5000, 10000. Leave empty to just toggle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral disclosure. It states the core action (toggle autoplay) but leaves ambiguity about whether providing a speed also toggles autoplay or only sets the speed, and how this interacts with an existing replay session. There is no mention of return values, state changes, or side effects, though the primary action is at least disclosed.

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, efficient sentence that front-loads the primary action and resource, then mentions the optional parameter. Every word carries meaning and there is 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?

The tool is simple, with one optional parameter and no output schema, but the description leaves unresolved how the speed parameter interacts with the toggle and what happens if replay mode is not active. The description is not grossly incomplete for a trivial tool, but additional context about state effects would make it more robust.

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?

The input schema already fully documents the speed parameter, including valid values and the note 'Leave empty to just toggle.' The tool description adds no additional meaning beyond what the schema provides. With 100% schema coverage, the baseline of 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 uses a specific verb 'Toggle' with a clear resource: 'autoplay in replay mode'. This distinguishes it from related siblings like replay_start, replay_step, and replay_stop, which focus on other replay controls. The optional speed is also mentioned, making the tool's scope immediately evident.

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 that this tool is used for controlling autoplay in replay mode, but it does not explicitly state when to use it versus alternatives such as replay_start or replay_step. There is no discussion of exclusions or conditions that would route an agent to a different sibling. Usage is largely inferred from the name and context.

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