Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by madiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

replay_start

Starts bar replay mode on a TradingView chart, optionally at a chosen date, to review or practice market movements bar by bar.

Instructions

Start bar replay mode, optionally at a specific date

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_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate to start replay from (YYYY-MM-DD format). If omitted, selects first available date.

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?

No annotations are provided, so the description carries the full burden of disclosing behavioral impact. It only says the action starts replay mode, but does not describe what changes in the UI/chart state, whether a prior replay session is reset, or what happens after invocation.

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 front-loaded sentence that states the verb, resource, and the one optional parameter. No filler or redundant phrasing.

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 tool with one optional parameter and a fully documented schema, the minimum invocation information is present. However, the description lacks sequencing context among replay_start, replay_step, replay_autoplay, and replay_stop, and does not explain what 'bar replay mode' entails beyond starting.

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 description coverage is 100%, so the schema already documents the date parameter fully. The description reinforces that the date is optional but adds no additional meaning beyond the schema.

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 clearly states a specific action with a specific resource: 'Start bar replay mode'. It also mentions the optional date, which distinguishes it from related replay tools like replay_step, replay_autoplay, and replay_stop by naming the entry point into the mode.

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?

The description gives no explicit guidance about when to use replay_start versus its sibling replay tools. The agent must infer from the tool name and sibling names that this is the entry point to replay mode, rather than being told.

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