Get OHLCV (candlestick) data for a trading pair
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of results to return (default: 100, max: 500) | |
| symbol | Yes | Trading pair symbol (e.g., BTC/USDT, INDY/USDT) | |
| exchange | Yes | Exchange to query. Supported: mexc, gateio, bitget, kraken | |
| timeframe | No | Candlestick timeframe (1m, 5m, 15m, 30m, 1h, 4h, 1d, 1w) | 1h |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure, yet it only states the basic fetch action. It does not mention whether the data is historical, how ordering or pagination behaves, what the response contains, or any rate-limits or safety characteristics, leaving an agent without useful behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler or redundancy. It efficiently states the action and resource, which is an ideal size for this simple data-fetch tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The schema completely documents all four parameters, including defaults and constraints, and OHLCV has a standard financial meaning, so the description is functionally adequate. However, with no output schema and no behavioral notes, details like candle ordering, whether the current incomplete candle is included, and the exact response structure remain unspecified, making the definition complete only at a minimal level.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents exchange, symbol, limit, and timeframe; the description adds no additional meaning beyond the schema. The phrase 'trading pair' maps to the symbol parameter but does not deepen understanding of any parameter, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Get') and a specific resource ('OHLCV (candlestick) data') for a trading pair, making the tool's function clear. It implicitly differentiates from siblings like get_ticker or get_trades, but it does not explicitly contrast itself with any alternative, so it falls just short of a top score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as get_ticker or get_trades, and no mention of use cases, prerequisites, or exclusions. The only implied usage is that an agent should call it when candlestick data is requested, but this is left entirely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct, but cancel_all_orders and stop_strategy both cancel all open orders for a trading pair, creating real ambiguity. The grid strategy tools are otherwise well-separated from the general exchange tools, though start_grid_strategy overlaps somewhat with create_order.
All tool names follow a consistent snake_case verb_noun pattern, such as get_ticker, list_orders, create_order, and stop_strategy. There are no mixed conventions or vague generic verbs.
Fifteen tools is at the upper edge of a well-scoped set, but each tool covers a meaningful operation across exchange trading, Cardano DEX data, and grid strategy management. The count feels slightly broad but not bloated.
The server provides solid coverage for trading workflows: market data, order management, balance retrieval, exchange discovery, and grid strategy lifecycle. Minor gaps exist, such as no way to fetch a specific historical order or modify an existing order, but core operations are covered.