Get OHLCV candlestick chart data for an AMM pool
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | REQUIRED: End timestamp (unix seconds) | |
| from | Yes | REQUIRED: Start timestamp (unix seconds) | |
| format | No | Response format: 'json' for raw data or 'markdown' for formatted text | markdown |
| poolId | Yes | The pool contract address or ID | |
| chainId | Yes | Chain ID where the pool is deployed (e.g., 'sonic') | |
| interval | Yes | REQUIRED: Candle interval |
Changes observed during successful MCP inspections.
Input schema / properties / from / descriptionPrevious value: -"Start timestamp (unix seconds)"New value: +"REQUIRED: Start timestamp (unix seconds)"Input schema / properties / interval / descriptionPrevious value: -"Candle interval (e.g., '1h', '4h', '1d')"New value: +"REQUIRED: Candle interval"Input schema / properties / interval / enumAdded value: +[
+ "1m",
+ "5m",
+ "15m",
+ "1h",
+ "4h",
+ "1d"
+]Input schema / properties / to / descriptionPrevious value: -"End timestamp (unix seconds)"New value: +"REQUIRED: End timestamp (unix seconds)"Input schema / requiredPrevious value: -[
- "chainId",
- "poolId"
-]New value: +[
+ "chainId",
+ "poolId",
+ "interval",
+ "from",
+ "to"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's a safe read. The description adds no additional behavioral context such as pagination, response format, or error behavior. It simply restates the tool's purpose without detailing any side effects or caveats.
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, focused sentence that avoids fluff. It is appropriately short, though it could arguably include a bit more context. It is front-loaded and efficient.
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?
Given the read-only annotations, complete schema, and no output schema, the description is minimally sufficient but lacks usage context and alternative differentiation. It states the resource but does not clarify when to choose this over related getters, making it complete only in a basic sense.
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%, with detailed descriptions for all six parameters, including enums and defaults. The description itself does not add parameter-level details beyond what the schema already provides, so it meets the baseline of 3.
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 it retrieves OHLCV candlestick data for an AMM pool, using a specific verb and resource. It distinguishes from sibling tools like get_amm_positions or get_orderbook by focusing on chart/candle data.
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 offers no guidance on when to use this tool over alternatives. It does not mention any prerequisites, use cases, or exclusions. Sibling tools exist but no differentiation 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.