DexPaprika (CoinPaprika)

Official

Overview Schema Source Related Servers Discussions Admin

getPoolOHLCV

Read-onlyIdempotent

Retrieve historical OHLCV price and volume data for a DEX pool over a specified time range, enabling price history analysis, charting, 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

Name	Required	Description	Default
`end`	No	OPTIONAL: End time for historical data (max 1 year from start)
`limit`	No	OPTIONAL: Number of data points to retrieve (default: 100, max: 366)
`start`	Yes	REQUIRED: Start time for historical data (Unix timestamp, RFC3339 timestamp, or yyyy-mm-dd format)
`network`	Yes	REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
`interval`	No	OPTIONAL: Interval granularity (default: '24h')	24h
`inversed`	No	OPTIONAL: Whether to invert the price ratio for alternative pair perspective (default: false)
`rationale`	Yes	REQUIRED. 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_address`	Yes	REQUIRED: Pool address or identifier

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ohlcv`	Yes	Open-High-Low-Close-Volume rows ordered by time_open ascending.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv1.0.1Jun 24, 2026

changedInput schema / properties / end / description

Previous value: -"End time for historical data (max 1 year from start)"New value: +"OPTIONAL: End time for historical data (max 1 year from start)"

changedInput schema / properties / interval / description

Previous value: -"Interval granularity: 1m, 5m, 10m, 15m, 30m, 1h, 6h, 12h, 24h"New value: +"OPTIONAL: Interval granularity (default: '24h')"

addedInput schema / properties / interval / enum

Added value: +[
+  "1m",
+  "5m",
+  "10m",
+  "15m",
+  "30m",
+  "1h",
+  "6h",
+  "12h",
+  "24h"
+]

changedInput schema / properties / inversed / description

Previous value: -"Whether to invert the price ratio for alternative pair perspective (e.g., ETH/USDC vs USDC/ETH)"New value: +"OPTIONAL: Whether to invert the price ratio for alternative pair perspective (default: false)"

changedInput schema / properties / limit / default
```
Previous value: -1New value: +100
```

changedInput schema / properties / limit / description

Previous value: -"Number of data points to retrieve (max 366) - adjust for different analysis needs"New value: +"OPTIONAL: Number of data points to retrieve (default: 100, max: 366)"

changedInput schema / properties / network / description

Previous value: -"Network ID from getNetworks (e.g., \"ethereum\", \"solana\")"New value: +"REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')"

removedInput schema / properties / poolAddress

Removed value: -{
-  "description": "Pool address or identifier",
-  "type": "string"
-}

addedInput schema / properties / pool_address

Added value: +{
+  "description": "REQUIRED: Pool address or identifier",
+  "type": "string"
+}

addedInput schema / properties / rationale

Added value: +{
+  "description": "REQUIRED. 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.",
+  "maxLength": 500,
+  "minLength": 20,
+  "type": "string"
+}

changedInput schema / properties / start / description

Previous value: -"Start time for historical data (Unix timestamp, RFC3339 timestamp, or yyyy-mm-dd format)"New value: +"REQUIRED: Start time for historical data (Unix timestamp, RFC3339 timestamp, or yyyy-mm-dd format)"

changedInput schema / required

Previous value: -[
-  "network",
-  "poolAddress",
-  "start"
-]New value: +[
+  "network",
+  "pool_address",
+  "start",
+  "rationale"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "ohlcv": {
+      "description": "Open-High-Low-Close-Volume rows ordered by time_open ascending.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "close": {
+            "type": "number"
+          },
+          "high": {
+            "type": "number"
+          },
+          "low": {
+            "type": "number"
+          },
+          "open": {
+            "type": "number"
+          },
+          "time_close": {
+            "description": "ISO 8601 timestamp of bucket close (inclusive at 23:59:59 for 24h).",
+            "type": "string"
+          },
+          "time_open": {
+            "description": "ISO 8601 timestamp of bucket open.",
+            "type": "string"
+          },
+          "volume": {
+            "description": "Trade volume in the bucket, in pair-quote units (or USD where applicable).",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "ohlcv"
+  ],
+  "type": "object"
+}

First observedAug 15, 2025

TDQS

A4.7/5.0

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.

Deploy Server