Skip to main content
Glama
kumarakshay2456

tradingview-mcp-india

coin_analysis

Analyze any cryptocurrency or stock on a specific exchange and timeframe, returning complete technical indicators and metrics.

Instructions

Get detailed analysis for a specific asset (coin or stock) on specified exchange and timeframe.

Args: symbol: Symbol — crypto: "BTCUSDT", "ETHUSDT"; stocks: "COMI" (EGX), "THYAO" (BIST), "600519" (SSE), "300251" (SZSE) exchange: Exchange — crypto: KUCOIN, BINANCE, MEXC; stocks: EGX, BIST, NASDAQ, NYSE, BURSA, HKEX, SSE, SZSE timeframe: Time interval (5m, 15m, 1h, 4h, 1D, 1W, 1M)

Returns: Detailed analysis with all indicators and metrics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
exchangeNoKUCOIN
timeframeNo15m
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states that it returns 'detailed analysis with all indicators and metrics' without mentioning side effects, authentication needs, rate limits, or whether it is read-only.

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 concisely structured with clear args and returns sections. Every sentence adds value, and the examples are compact yet informative. No wasted words.

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?

The description adequately covers the parameters and returns a detailed analysis, but lacks specifics on what indicators and metrics are included. Given the absence of an output schema, more detail on the output format would improve completeness.

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

Parameters5/5

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

The description adds substantial meaning beyond the input schema by providing concrete examples for symbol (crypto and stock formats), exchange (list of valid exchanges), and timeframe (allowed intervals). With 0% schema coverage, this is essential and well-executed.

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?

Description clearly states it provides detailed analysis for a specific asset on an exchange and timeframe, with examples of symbols and exchanges. However, it does not explicitly differentiate from sibling tools like advanced_candle_pattern or bollinger_scan, which also provide analysis.

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?

No guidance on when to use this tool versus alternatives. The description lists examples but does not explain when to prefer coin_analysis over other analysis tools like multi_timeframe_analysis or market_snapshot.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kumarakshay2456/tradingview-mcp-india'

If you have feedback or need assistance with the MCP directory API, please join our Discord server