get_candlesGet OHLCV candles for a market at a given resolution. Useful for trend/volatility analysis.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| toISO | No | ISO 8601 end time | |
| market | Yes | Market ticker, e.g. BTC-USD | |
| fromISO | No | ISO 8601 start time | |
| resolution | Yes | Candle resolution |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description indicates the tool is read-only (annotations already set readOnlyHint=true) and focuses on retrieving data. It does not add behavioral details such as rate limits, pagination, or data ordering, but it is consistent with annotations.
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 two sentences, front-loaded with the core action, and contains no extraneous information. Every word is necessary.
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 description explains the tool's purpose and use case, but given the lack of an output schema, it does not describe the return format (e.g., array of candle objects). This is a minor gap for a simple data retrieval tool.
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 coverage is 80% (all required parameters and most optional have descriptions). The tool description does not elaborate on parameters beyond what the schema provides, so it meets baseline but adds no extra meaning.
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 clearly states the action ('Get'), the resource ('OHLCV candles'), and the key parameters ('for a market at a given resolution'). It also implies a singular market, distinguishing it from the sibling get_candles_multi.
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?
The description mentions it is 'useful for trend/volatility analysis', which provides a use case but does not explicitly state when to use this tool versus alternatives like get_candles_multi or other analytical tools. No exclusionary guidance is provided.
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 there is overlap among the read-heavy account tools: get_balance/get_funding_status/fund virtually duplicate each other, and get_equity/get_portfolio/get_position_risk/get_open_orders/get_positions all converge on equity and open-position data. The detailed descriptions help an agent choose, but several tools have fuzzy boundaries.
The overwhelming majority follow the expected verb_noun convention: get_*, place_*, cancel_*, close_*. Minor deviations such as batch_cancel, get_candles_multi, top_up_gas, and whoami make the pattern not perfectly uniform, but the inconsistency is small.
At 33 tools, the surface is beyond what most agents need and includes several redundant query helpers rather than genuinely distinct operations. A broad exchange can justify a large surface, but get_balance/get_funding_status, get_equity/get_portfolio/get_position_risk, and get_candles/get_candles_multi make the set feel top-heavy.
The core lifecycle is well covered: market discovery, market data, order placement/cancellation, position management, risk, funding transfers, PnL, and account status. Obvious gaps are limited to historical order lookup by order ID, a way to cancel across all markets in one call, and a few optional account-history conveniences.