Skip to main content
Glama
Sign In
tradingview-capture

tradingview-capture

by sunkailun1992
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

symbol_data

Exports structured TradingView chart data for a specific symbol—identity, tables, labels, lines, boxes, last values, drawings, inputs, plots, and optional CSV rows—to local files for analysis.

Instructions

Structured data for one symbol. parts: identity, tables, labels, lines, boxes, lastValues, drawings, readiness, inputs, plots, colors, fills, bands, notExported (default identity, tables, lastValues, drawings). series_last adds the last N CSV rows.

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": {
      "output_dir": "<output_dir>",
      "symbol": "<symbol>"
    },
    "name": "symbol_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
partsNo
symbolYes
output_dirYes
series_lastNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it never discloses read-vs-write behavior, that a required output_dir implies files written to disk, or any side effects/overwrite semantics. The parts enumeration is the only substantive disclosure.

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?

Dense and front-loaded: scope first, then the parts vocabulary, then the series_last modifier. Single paragraph with no filler, though the parts list is long enough to be hard to scan in prose.

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?

An output schema exists so return values need not be described, and the parts vocabulary is covered. But for a 4-parameter tool with no annotations and zero schema coverage, omitting what symbol identifies and what output_dir does leaves an agent guessing at required inputs.

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 0%, so the description must compensate. It does well for parts (full enumerated list plus defaults) and series_last (last N CSV rows), but says nothing about the two required parameters, symbol and output_dir, leaving half the schema uninterpreted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Structured data for one symbol" states the resource and scope, and the enumerated parts list makes the tool's output concrete. However, it lacks a real verb (extract/export?) and never says whether the data is returned or written to disk, so the purpose is only partly pinned down against the capture-oriented siblings.

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 statement of when to use this versus the siblings (capture_start, batch_summary, diagnose) or what makes a symbol eligible. The only guidance is a default-parts note and what series_last appends, which is configuration rather than usage selection.

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