Skip to main content
Glama
coinpaprika

DexPaprika (CoinPaprika)

Official

getPoolOHLCV

Read-onlyIdempotent

Retrieve historical OHLCV price candles for any DEX pool over a time range, enabling price charts and backtesting.

Instructions

Get historical OHLCV candles (open, high, low, close, volume) for one pool over a time range, returned as a time-series array. Read-only and keyless. Use for 'price history of this pair', 'hourly chart for the last week', 'candles since Jan 1', or backtesting; for the single current price use getPoolDetails instead. Params: network (required); pool_address (required); start (required; Unix timestamp, RFC3339, or yyyy-mm-dd); end (optional, capped to 1 year after start); interval one of '1m','5m','10m','15m','30m','1h','6h','12h','24h' (default '24h'); limit (default 100, max 366 candles); inversed (optional bool, default false).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoOPTIONAL: End time for historical data (max 1 year from start)
limitNoOPTIONAL: Number of data points to retrieve (default: 100, max: 366)
startYesREQUIRED: Start time for historical data (Unix timestamp, RFC3339 timestamp, or yyyy-mm-dd format)
networkYesREQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
intervalNoOPTIONAL: Interval granularity (default: '24h')24h
inversedNoOPTIONAL: Whether to invert the price ratio for alternative pair perspective (default: false)
rationaleYesREQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions` field for the full convention and worked examples.
pool_addressYesREQUIRED: Pool address or identifier

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ohlcvYesOpen-High-Low-Close-Volume rows ordered by time_open ascending.
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds 'Read-only and keyless' and notes that end is capped to 1 year after start, providing useful behavioral context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single long sentence but front-loaded with purpose and usage. While comprehensive, it could be more concise with bullet points. No superfluous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters, 4 required, and an output schema present, the description covers all necessary aspects: purpose, usage, parameter details, and sibling differentiation. Leaves no gaps for an agent.

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 coverage is 100%, but description adds extra meaning: accepted formats for start (Unix timestamp, RFC3339, yyyy-mm-dd), cap on end, interval granularities, and default values. Significantly enriches the schema.

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?

Explicitly states it retrieves historical OHLCV candles for one pool over a time range, with specific verb 'Get' and resource 'OHLCV candles'. Clearly distinguishes from sibling 'getPoolDetails' for current price.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit usage examples ('price history of this pair', 'hourly chart for the last week') and explicitly names alternative tool ('use getPoolDetails instead').

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/coinpaprika/dexpaprika-mcp'

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