Skip to main content
Glama
Sign In
tradingview-capture

tradingview-capture

by sunkailun1992
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

capture_start

Starts a background job that captures charts from a TradingView Desktop layout into a target folder and returns a job ID immediately; optionally loads historical data first.

Instructions

Start capturing TradingView codes from one TradingView Desktop layout into output_dir. Returns a job id at once. history_from (YYYY-MM-DD, optional) first loads each chart's history back to 00:00 UTC on that date, or as far as TradingView goes.

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": {
      "layout": "<layout>",
      "symbols": "<symbols>",
      "output_dir": "<output_dir>"
    },
    "name": "capture_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
layoutYes
symbolsYes
timeframeNo1D
output_dirYes
history_fromNo
required_studiesNo
ready_timeout_secNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool returns a job id immediately and that history_from preloads chart history back to a specified date or as far as TradingView goes. It does not describe side effects, required permissions, failure behavior, job lifecycle, timeout behavior, or what happens if required studies are missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, front-loaded with the main action and async behavior, with no obvious filler. The history_from detail is relevant and appropriately placed after the core operation.

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

Completeness2/5

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

This is a complex seven-parameter, no-annotation operation with an output schema. The description covers the async start and history preloading, but omits key parameter meanings such as symbols, timeframe, required_studies, and ready_timeout_sec, and it does not explain the expected follow-up workflow with capture_status or capture_retry.

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

Parameters2/5

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

Schema description coverage is 0% across all seven parameters, so the description must compensate. It explains layout, output_dir, and history_from, including the date format and semantics, but leaves symbols, timeframe, required_studies, and ready_timeout_sec undocumented beyond their bare schema titles.

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 action: start capturing TradingView codes from one TradingView Desktop layout into output_dir. It also clarifies that the call is asynchronous by returning a job id at once. It does not explicitly distinguish itself from siblings such as capture_status or capture_retry, but the 'start' and job-id language makes the role reasonably clear.

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 this is the tool to use when initiating a capture job, and the immediate job-id return hints that polling should happen elsewhere. However, it never names capture_status, capture_retry, or any alternative, and gives no explicit when-to-use or when-not-to-use guidance. Usage is therefore only implicit.

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