Skip to main content
Glama

getPoolOHLCV

Retrieve historical OHLCV (Open, High, Low, Close, Volume) data for cryptocurrency pools to analyze price trends, perform backtesting, and create visualizations across multiple blockchain networks.

Instructions

Get historical price data (OHLCV) for a pool - essential for price analysis, backtesting, and visualization. Requires network and pool address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYesNetwork ID from getNetworks (e.g., "ethereum", "solana")
poolAddressYesPool address or identifier
startYesStart time for historical data (Unix timestamp, RFC3339 timestamp, or yyyy-mm-dd format)
endNoEnd time for historical data (max 1 year from start)
limitNoNumber of data points to retrieve (max 366) - adjust for different analysis needs
intervalNoInterval granularity: 1m, 5m, 10m, 15m, 30m, 1h, 6h, 12h, 24h24h
inversedNoWhether to invert the price ratio for alternative pair perspective (e.g., ETH/USDC vs USDC/ETH)

Implementation Reference

  • src/index.js:189-209 (registration)
    Registration of the getPoolOHLCV tool using server.tool(), including name, description, input schema, and handler function.
    server.tool(
      'getPoolOHLCV',
      'Get historical price data (OHLCV) for a pool - essential for price analysis, backtesting, and visualization. Requires network and pool address.',
      {
        network: z.string().describe('Network ID from getNetworks (e.g., "ethereum", "solana")'),
        poolAddress: z.string().describe('Pool address or identifier'),
        start: z.string().describe('Start time for historical data (Unix timestamp, RFC3339 timestamp, or yyyy-mm-dd format)'),
        end: z.string().optional().describe('End time for historical data (max 1 year from start)'),
        limit: z.number().optional().default(1).describe('Number of data points to retrieve (max 366) - adjust for different analysis needs'),
        interval: z.string().optional().default('24h').describe('Interval granularity: 1m, 5m, 10m, 15m, 30m, 1h, 6h, 12h, 24h'),
        inversed: z.boolean().optional().default(false).describe('Whether to invert the price ratio for alternative pair perspective (e.g., ETH/USDC vs USDC/ETH)')
      },
      async ({ network, poolAddress, start, end, limit, interval, inversed }) => {
        let endpoint = `/networks/${network}/pools/${poolAddress}/ohlcv?start=${encodeURIComponent(start)}&interval=${interval}&limit=${limit}&inversed=${inversed}`;
        if (end) {
          endpoint += `&end=${encodeURIComponent(end)}`;
        }
        const data = await fetchFromAPI(endpoint);
        return formatMcpResponse(data);
      }
    );
  • Zod schema defining the input parameters for the getPoolOHLCV tool.
    {
      network: z.string().describe('Network ID from getNetworks (e.g., "ethereum", "solana")'),
      poolAddress: z.string().describe('Pool address or identifier'),
      start: z.string().describe('Start time for historical data (Unix timestamp, RFC3339 timestamp, or yyyy-mm-dd format)'),
      end: z.string().optional().describe('End time for historical data (max 1 year from start)'),
      limit: z.number().optional().default(1).describe('Number of data points to retrieve (max 366) - adjust for different analysis needs'),
      interval: z.string().optional().default('24h').describe('Interval granularity: 1m, 5m, 10m, 15m, 30m, 1h, 6h, 12h, 24h'),
      inversed: z.boolean().optional().default(false).describe('Whether to invert the price ratio for alternative pair perspective (e.g., ETH/USDC vs USDC/ETH)')
    },
  • Handler function that constructs the API endpoint for pool OHLCV data and fetches it using the shared fetchFromAPI helper, then formats the response.
    async ({ network, poolAddress, start, end, limit, interval, inversed }) => {
      let endpoint = `/networks/${network}/pools/${poolAddress}/ohlcv?start=${encodeURIComponent(start)}&interval=${interval}&limit=${limit}&inversed=${inversed}`;
      if (end) {
        endpoint += `&end=${encodeURIComponent(end)}`;
      }
      const data = await fetchFromAPI(endpoint);
      return formatMcpResponse(data);
    }
  • Shared helper function used by getPoolOHLCV (and other tools) to make API requests to DexPaprika and handle errors.
    async function fetchFromAPI(endpoint) {
      try {
        const response = await fetch(`${API_BASE_URL}${endpoint}`);
        if (!response.ok) {
          if (response.status === 410) {
            throw new Error(
              'This endpoint has been permanently removed. Please use network-specific endpoints instead. ' +
              'For example, use /networks/{network}/pools instead of /pools. ' +
              'Get available networks first using the getNetworks function.'
            );
          }
          if (response.status === 429) {
            throw new Error(
              'Rate limit exceeded. You have reached the maximum number of requests allowed for the free tier. ' +
              'To increase your rate limits and access additional features, please consider upgrading to a paid plan at https://docs.dexpaprika.com/'
            );
          }
          throw new Error(`API request failed with status ${response.status}`);
        }
        return await response.json();
      } catch (error) {
        console.error(`Error fetching from API: ${error.message}`);
        throw error;
      }
    }
  • Shared helper function used by getPoolOHLCV (and other tools) to format API responses in MCP-compatible structure.
    function formatMcpResponse(data) {
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data)
          }
        ]
      };
    }
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Requires network and pool address' which indicates prerequisites, but doesn't mention rate limits, authentication needs, error conditions, or what happens with invalid parameters. The description doesn't contradict annotations (none exist), but provides only basic operational context.

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

Conciseness5/5

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

Two sentences with zero waste. First sentence states purpose and use cases, second sentence highlights key requirements. Every word serves a clear purpose, and the most critical information (what it does and what it needs) is front-loaded.

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

Completeness3/5

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

For a 7-parameter tool with no annotations and no output schema, the description provides basic operational context but lacks details about return format, error handling, or performance characteristics. The schema covers parameters well, but the description doesn't compensate for the absence of output schema or behavioral annotations, leaving gaps in complete understanding.

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 description coverage is 100%, so all parameters are well-documented in the schema. The description adds minimal value beyond the schema by mentioning 'Requires network and pool address' (which aligns with required parameters) and framing the tool's purpose. Since schema does the heavy lifting, baseline would be 3, but the description's concise reinforcement of key requirements earns a slightly higher score.

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?

The description clearly states the specific action ('Get historical price data'), the resource ('for a pool'), and the data format ('OHLCV'). It distinguishes this tool from siblings like getPoolDetails or getPoolTransactions by focusing on price history rather than general pool information or transaction data.

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

Usage Guidelines3/5

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

The description mentions 'essential for price analysis, backtesting, and visualization' which implies usage contexts, but doesn't explicitly state when to use this tool versus alternatives like getPoolDetails for non-price information or getStats for aggregated statistics. No explicit exclusions or comparisons to siblings are provided.

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

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