DexPaprika

getPoolOHLCV

Read-onlyIdempotent

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; easiest as a relative offset from now such as '-24h' or '-7d', so you need not know today's date; also Unix seconds, RFC3339 or yyyy-mm-dd); end (optional); interval one of '1m','5m','10m','15m','30m','1h','6h','12h','24h' (default '24h'); limit (default 100, max 1000 candles); inversed (optional bool, default false). This server serves candles as a free DexPaprika key gets them: interval '10m' or longer, start and end within the last 7 days; outside that, it runs on the caller's own Dev, Pro or Enterprise key when the connection carries one (the Authorization header, the key on its own), and otherwise returns DP403_PLAN_REQUIRED and sends nothing upstream.

Input Schema

Name	Required	Description	Default
`end`	No	OPTIONAL: End time for historical data, same formats as start (e.g. '-1h')
`limit`	No	OPTIONAL: Number of OHLCV data points to retrieve (default: 100, max: 1000). One row per `interval`.
`start`	Yes	REQUIRED: Start time. A relative offset from now is simplest and needs no knowledge of today's date: '-24h' (last 24 hours), '-7d', '-90m' (units s, m, h, d). Also accepts RFC3339 (e.g. '2024-01-01T00:00:00Z'), Unix epoch seconds and YYYY-MM-DD (treated as 00:00:00 UTC).
`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

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.

Changed4 schema fields changedOct 23, 2026

removedOutput schema / properties / ohlcv / items / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties / ohlcv / items / anyOf

Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "close": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "high": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "low": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "open": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "time_close": {
+        "description": "ISO 8601 timestamp of bucket close (inclusive at 23:59:59 for 24h).",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "time_open": {
+        "description": "ISO 8601 timestamp of bucket open.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "volume": {
+        "description": "Trade volume in the bucket, in pair-quote units (or USD where applicable).",
+        "type": [
+          "number",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / ohlcv / items / properties

Removed value: -{
-  "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"
-  }
-}

removedOutput schema / properties / ohlcv / items / type
```
Removed value: -"object"
```

Changed3 schema fields changedSep 28, 2026

changedInput schema / properties / end / description

Previous value: -"OPTIONAL: End time for historical data (max 1 year from start)"New value: +"OPTIONAL: End time for historical data, same formats as start (e.g. '-1h')"

changedInput schema / properties / limit / description

Previous value: -"OPTIONAL: Number of OHLCV data points to retrieve (default: 100, max: 366). One row per `interval`."New value: +"OPTIONAL: Number of OHLCV data points to retrieve (default: 100, max: 1000). One row per `interval`."

changedInput schema / properties / start / description

Previous value: -"REQUIRED: Start time. RFC3339 recommended (e.g. '2024-01-01T00:00:00Z'). Also accepts Unix epoch seconds and YYYY-MM-DD (treated as 00:00:00 UTC)."New value: +"REQUIRED: Start time. A relative offset from now is simplest and needs no knowledge of today's date: '-24h' (last 24 hours), '-7d', '-90m' (units s, m, h, d). Also accepts RFC3339 (e.g. '2024-01-01T00:00:00Z'), Unix epoch seconds and YYYY-MM-DD (treated as 00:00:00 UTC)."

Changed1 schema field changedSep 2, 2026

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 observedJul 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds critical context beyond them: the free-tier key limits (interval '10m' or longer, start/end within 7 days), the fallback to caller-supplied Dev/Pro/Enterprise keys via Authorization header, and the DP403_PLAN_REQUIRED error otherwise. These are non-obvious operational constraints that materially affect invocation.

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?

The definition is dense but front-loads purpose, then alternatives, then parameters, then constraints. It is longer than ideal because the parameter list repeats schema details, but no sentence is wasted given the complexity of the tool and its plan constraints.

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 a rich output schema (time-series array), the description need not explain return values; it covers purpose, usage, parameters, and operational limits thoroughly. An agent has everything needed to call correctly or handle the plan-required error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; however, the description adds meaning by clarifying that start is easiest as a relative offset (so the caller need not know today's date) and by linking interval and start/end constraints to plan requirements. It largely echoes the schema but does so usefully and adds the key parameter-level constraint.

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?

States a specific verb and resource ('Get historical OHLCV candles ... for one pool over a time range') and distinguishes itself from the sibling getPoolDetails for current price. An agent can immediately tell what it returns and how it differs from adjacent tools.

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?

Explicitly lists use cases ('price history of this pair', 'hourly chart for the last week', backtesting) and names the alternative (getPoolDetails) with the condition that selects it. This is exactly the when-to-use guidance needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DexPaprika tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?