Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by moeuu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Import OHLCV CSV

chart_import_csv

Load a CSV file (time/open/high/low/close, volume optional) into a chart by providing its path, market symbol, and bar interval.

Instructions

Load a CSV under MARKET_CHART_DATA_ROOT into the chart. Required columns: time (or timestamp/date), open, high, low, close; volume is optional.

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": {
      "path": "<path>",
      "symbol": "<symbol>",
      "interval": "<interval>"
    },
    "name": "chart_import_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesCSV path inside MARKET_CHART_DATA_ROOT. Columns: time/open/high/low/close/volume.
symbolYesMarket symbol, preferably EXCHANGE:TICKER (for example NASDAQ:AAPL).
intervalYesBar interval such as 1, 5, 60, 1D, 1W, or 1M.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

The description makes clear that this operation loads CSV data into the chart and lists the required columns, but it does not disclose side effects such as whether existing chart data is replaced, appended, or whether errors occur for malformed files. Annotations provide no read-only/idempotency assurances, and the description does not fill that gap beyond the basic load behavior.

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 one focused sentence with no filler. It front-loads the core action and then adds only the essential column requirements.

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 straightforward import tool, the description combined with the schema covers the source path, required parameters, and CSV content requirements. It does not explain return values or behavior on invalid data, but those are not strongly necessary for a simple CSV import given the context provided.

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 all three parameters with 100% coverage, so the baseline is 3. The description adds useful file-content semantics above the schema by noting the time column can be 'timestamp/date' and that volume is optional, which helps agents prepare valid CSV inputs.

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 + resource: 'Load a CSV under MARKET_CHART_DATA_ROOT into the chart' and identifies the required OHLCV columns. It clearly distinguishes this import tool from chart viewing or indicator tools among the siblings.

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 provides clear context about when to use the tool by specifying the source location (CSV under MARKET_CHART_DATA_ROOT) and target (the chart). It does not explicitly name alternative tools for situations where CSV import is not appropriate, but the path restriction and column requirements imply the intended use.

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