Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by moeuu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set chart view

chart_set_view

Update chart theme, symbol, or interval without reloading data. Adjust display settings instantly for focused analysis.

Instructions

Change chart metadata or theme without fetching data.

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": "chart_set_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNo
symbolNoMarket symbol, preferably EXCHANGE:TICKER (for example NASDAQ:AAPL).
intervalNoBar interval such as 1, 5, 60, 1D, 1W, or 1M.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations are present but unhelpful (all hints false). The description adds the behavioral trait that no data fetching occurs, but for a mutating tool it does not disclose side effects, persistence behavior, or whether changes apply to the current chart view. No contradiction with annotations is present.

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 a single sentence that conveys the core purpose and scope with no wasted words. It is front-loaded and easy to parse.

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 tool with three optional parameters, no output schema, and no nested objects, the description plus schema cover the essential behavior. The main gap is the absence of usage alternatives, but the tool complexity is low enough that the description is largely complete.

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 67%, with symbol and interval already documented in the schema. The description broadly groups parameters as 'metadata or theme' but does not add meaningful semantics beyond that grouping. This is adequate but not exceptional.

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 clear action—'Change chart metadata or theme'—and adds a scope qualifier 'without fetching data' that helps distinguish it from data-fetching siblings. It is not quite a 5 because 'metadata' is somewhat vague and does not explicitly name symbol/interval/theme fields.

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 phrase 'without fetching data' implies when not to use this tool, but there is no explicit when-to-use guidance, no exclusion of alternatives, and no mention of related tools like chart_set_data or chart_get_state. The agent must infer the intended use case from the description alone.

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