Skip to main content
Glama
kumarakshay2456

tradingview-mcp-india

multi_agent_analysis

Runs a multi-agent debate combining technical, sentiment, and risk analyses to deliver a final trading decision for any symbol and exchange.

Instructions

Run a multi-agent debate (Technical, Sentiment, Risk) for a specific symbol.

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

Returns: A structured debate between 3 AI agents culminating in a final trading decision.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
exchangeNoKUCOIN
timeframeNo15m
Behavior4/5

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

The description discloses the core behavior: a structured debate among three AI agents culminating in a trading decision. With no annotations provided, this is adequate but lacks details on data sources (real-time vs historical) or rate limits.

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 concise, front-loaded with the purpose, and uses a clear Args/Returns structure. Every sentence adds value with no wasted words.

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?

Given the complexity of a multi-agent debate tool, the description covers inputs well with examples but omits details about the debate structure or output format. However, it states the outcome (final trading decision), which is sufficient for basic usage.

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 significant meaning beyond the bare input schema by providing concrete examples for each parameter (e.g., symbol 'BTCUSDT', exchange 'KUCOIN', timeframe '15m') and clarifying acceptable values across asset classes. This compensates for the schema's lack of descriptions and enums.

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 clearly states the action ('Run a multi-agent debate'), the resource ('Technical, Sentiment, Risk'), and the scope ('for a specific symbol'). It distinguishes itself from sibling technical indicator tools by focusing on a debate of agents.

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 description implies this tool is for multi-perspective analysis but does not explicitly state when to use it over alternatives like combined_analysis or coin_analysis. No exclusions or when-not guidance is provided.

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