Skip to main content
Glama
btanaji

TradingView MCP

by btanaji

advanced_candle_pattern

Read-only

Identify advanced candle patterns across multiple timeframes. Configure exchange, timeframe, and pattern length to spot significant size increases.

Instructions

Advanced candle pattern analysis using multi-timeframe data.

Args: exchange: Exchange name (BINANCE, KUCOIN, etc.) base_timeframe: Base timeframe for analysis (5m, 15m, 1h, 4h) pattern_length: Number of consecutive periods to analyse (2-4) min_size_increase: Minimum percentage increase in candle size limit: Maximum number of results to return

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
exchangeNoKUCOIN
base_timeframeNo15m
pattern_lengthNo
min_size_increaseNo
Behavior3/5

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

Annotations already cover readOnlyHint=true and destructiveHint=false, so the safety profile is disclosed. The description adds the multi-timeframe behavioral aspect and parameter constraints, but does not reveal return format or other operational details. This is acceptable given annotation coverage, but not rich.

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 appropriately concise: one purpose sentence followed by an Args list. Every line carries useful information and it is front-loaded with the core purpose.

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 covers purpose and all parameters, but lacks return-value information (no output schema exists) and does not distinguish itself from sibling tools like multi_timeframe_analysis. These gaps are notable given the absence of structured output documentation.

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?

Schema description coverage is 0%, but the description's Args section provides clear explanations for all five parameters, including concrete examples and ranges (e.g., 'BINANCE, KUCOIN', '5m, 15m, 1h, 4h', '2-4'). This fully compensates for the schema's lack of descriptions.

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 clearly states the tool performs 'advanced candle pattern analysis using multi-timeframe data,' which is a specific verb+resource combination. However, it does not explicitly differentiate from sibling tools like consecutive_candles_scan or multi_timeframe_analysis, so it misses full distinction.

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 gives some context ('using multi-timeframe data') implying when this tool is appropriate, but it offers no explicit when-to-use/when-not-to-use guidance or references to alternatives. This is enough for an implied usage but not clear directional guidance.

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/btanaji/tradingview-mcp'

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