Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by madiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

symbol_info

Retrieve detailed metadata for the current TradingView symbol, including name, exchange, type, and description, to identify and contextualize the active chart instrument.

Instructions

Get detailed metadata about the current symbol (name, exchange, type, description)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must communicate behavior on its own. 'Get' signals a non-mutating read and the parenthetical names the data fields, which is useful. However, it does not disclose whether an active chart or session is required or the shape and format of the returned metadata, leaving some behavioral ambiguity for an agent.

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?

A single sentence gets straight to the point: the verb, resorce, and returned fields are front-loaded with no filler. Every word contributes to understanding the tool.

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?

For a zero-parameter getter this is mostly adequate, but with no output schema the description should more explicitly describe the return value and any precondition such as an active chart with a selected symbol. The listed fields hint at the return payload but do not fully specify it.

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 input schema has zero parameters and 100% schema description coverage, so the baseline is 4. The description adds context that the operation is scoped to the 'current symbol', which is the only relevant semantics; there are no parameter details needed.

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 uses the explicit verb 'Get' and identifies a specific resource, the current symbol's metadata, while listing the fields returned. It is not a tautology, but it does not explicitly compare itself to sibling tools such as symbol_search or quote_get, so it stops short of full sibling differentiation.

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 phrase 'current symbol' implies the tool should be used when a symbol is already loaded or selected, but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives like symbol_search or quote_get. The usage context is therefore only implied, not stated.

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