Skip to main content
Glama
FerroxLabs

TVControl

by FerroxLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

replay_start

Start TradingView bar replay at a specified date, rejecting dates outside replay depth to avoid silent cursor relocation. Optionally allow relocation when the requested date is unavailable.

Instructions

Start bar replay mode, optionally at a specific date. A date outside this symbol/timeframe replay depth is REFUSED rather than silently relocated - every read taken after a relocation is correct for a date you did not ask for.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate to start replay from (YYYY-MM-DD format). If omitted, selects first available date.
allow_relocationNoAccept a cursor TradingView moved to a different date because the requested one is outside replay depth. The result still carries relocated:true and the real current_date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.3
    • addedInput schema / properties / allow_relocation
      Added value: +{
+  "description": "Accept a cursor TradingView moved to a different date because the requested one is outside replay depth. The result still carries relocated:true and the real current_date.",
+  "type": "boolean"
+}
  2. First observedv2.2.1

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well. It explicitly discloses that out-of-depth dates are refused rather than silently relocated, and explains the reasoning: reads after a relocation are correct for a date the user did not ask for. This is valuable, non-obvious behavioral information.

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?

Two sentences only. The core action is front-loaded, and the second sentence provides a critical caveat without any filler. Every word contributes to helping the agent use the tool correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter tool, the description covers the core behavior and an important edge case. It does not describe the return value or behavior when called again while already in replay mode, but the sibling tool set and tool context make these gaps minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents both parameters with descriptions, so most parameter semantics are covered. The description adds meaning by explaining the consequence of requesting an unavailable date and warns about the relocation effect, which enriches the understanding of the date and allow_relocation parameters.

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 and resource: 'Start bar replay mode'. It also clarifies the optional date behavior, making it clearly distinct from sibling tools like replay_stop, replay_step, and replay_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes it clear this is the entry point for bar replay mode and how the date parameter behaves. It does not explicitly name alternatives or exclusion criteria, but its role is evident from the verb 'Start' and the sibling tool names.

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