Skip to main content
Glama
coinpaprika

DexPaprika (CoinPaprika)

Official

getTokenPools

Find liquidity pools containing a specific token on a blockchain network to identify where the token is traded, with options to filter, sort, and paginate results.

Instructions

Get liquidity pools containing a specific token on a network. Great for finding where a token is traded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYesNetwork ID from getNetworks (e.g., "ethereum", "solana")
tokenAddressYesToken address or identifier
pageNoPage number for pagination
limitNoNumber of items per page (max 100)
sortNoSort orderdesc
orderByNoField to order byvolume_usd
reorderNoIf true, reorders the pool so that the specified token becomes the primary token for all metrics
addressNoFilter pools that contain this additional token address

Implementation Reference

  • The core handler function for the 'getTokenPools' tool. It constructs the API endpoint for fetching liquidity pools containing the specified token on a given network, handles optional parameters like pagination, sorting, reordering, and additional address filtering, fetches the data using the fetchFromAPI helper, and formats the response.
    async ({ network, tokenAddress, page, limit, sort, orderBy, reorder, address }) => {
      let endpoint = `/networks/${network}/tokens/${tokenAddress}/pools?page=${page}&limit=${limit}&sort=${sort}&order_by=${orderBy}`;
      if (reorder !== undefined) {
        endpoint += `&reorder=${reorder}`;
      }
      if (address) {
        endpoint += `&address=${encodeURIComponent(address)}`;
      }
      const data = await fetchFromAPI(endpoint);
      return formatMcpResponse(data);
    }
  • Zod schema defining the input parameters for the 'getTokenPools' tool, including required network and tokenAddress, and optional pagination, sorting, and filtering params.
    {
      network: z.string().describe('Network ID from getNetworks (e.g., "ethereum", "solana")'),
      tokenAddress: z.string().describe('Token address or identifier'),
      page: z.number().optional().default(0).describe('Page number for pagination'),
      limit: z.number().optional().default(10).describe('Number of items per page (max 100)'),
      sort: z.enum(['asc', 'desc']).optional().default('desc').describe('Sort order'),
      orderBy: z.enum(['volume_usd', 'price_usd', 'transactions', 'last_price_change_usd_24h', 'created_at']).optional().default('volume_usd').describe('Field to order by'),
      reorder: z.boolean().optional().describe('If true, reorders the pool so that the specified token becomes the primary token for all metrics'),
      address: z.string().optional().describe('Filter pools that contain this additional token address')
    },
  • src/index.js:168-192 (registration)
    Registration of the 'getTokenPools' tool using McpServer.tool method, specifying name, description, input schema, and handler function.
    server.tool(
      'getTokenPools',
      'Get liquidity pools containing a specific token on a network. Great for finding where a token is traded.',
      {
        network: z.string().describe('Network ID from getNetworks (e.g., "ethereum", "solana")'),
        tokenAddress: z.string().describe('Token address or identifier'),
        page: z.number().optional().default(0).describe('Page number for pagination'),
        limit: z.number().optional().default(10).describe('Number of items per page (max 100)'),
        sort: z.enum(['asc', 'desc']).optional().default('desc').describe('Sort order'),
        orderBy: z.enum(['volume_usd', 'price_usd', 'transactions', 'last_price_change_usd_24h', 'created_at']).optional().default('volume_usd').describe('Field to order by'),
        reorder: z.boolean().optional().describe('If true, reorders the pool so that the specified token becomes the primary token for all metrics'),
        address: z.string().optional().describe('Filter pools that contain this additional token address')
      },
      async ({ network, tokenAddress, page, limit, sort, orderBy, reorder, address }) => {
        let endpoint = `/networks/${network}/tokens/${tokenAddress}/pools?page=${page}&limit=${limit}&sort=${sort}&order_by=${orderBy}`;
        if (reorder !== undefined) {
          endpoint += `&reorder=${reorder}`;
        }
        if (address) {
          endpoint += `&address=${encodeURIComponent(address)}`;
        }
        const data = await fetchFromAPI(endpoint);
        return formatMcpResponse(data);
      }
    );
  • Helper function to make API requests to DexPaprika, handles errors like 410 (deprecated endpoint) and 429 (rate limit), used by getTokenPools handler.
    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;
      }
    }
  • Helper function to format API response data into MCP-compatible content structure, used by getTokenPools and other tools.
    function formatMcpResponse(data) {
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data)
          }
        ]
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description mentions the tool is 'great for finding where a token is traded,' which hints at a read-only lookup function, but doesn't explicitly state whether it's a read operation, what permissions are needed, or any rate limits. For a tool with 8 parameters and no annotation coverage, this leaves significant behavioral gaps.

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?

The description is extremely concise (two sentences) and front-loaded with the core purpose. Every sentence earns its place: the first states what the tool does, and the second provides usage context. There's zero wasted verbiage.

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?

Given the tool's complexity (8 parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and hints at usage but lacks behavioral details (e.g., pagination behavior, error cases, or response format). For a read-focused tool with rich schema documentation, it's passable but leaves room for improvement in contextual guidance.

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

Parameters3/5

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

Schema description coverage is 100%, meaning all parameters are well-documented in the schema itself. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., it doesn't explain the 'reorder' parameter's effect or provide examples). With high schema coverage, the baseline is 3, as the description doesn't compensate but doesn't need to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get liquidity pools containing a specific token on a network.' It specifies the verb ('Get'), resource ('liquidity pools'), and scope ('containing a specific token on a network'). However, it doesn't explicitly differentiate from sibling tools like 'getNetworkPools' or 'getDexPools' beyond the token-specific focus.

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 provides implied usage context: 'Great for finding where a token is traded.' This suggests the tool is for discovering trading venues for a token. However, it doesn't explicitly state when to use this tool versus alternatives like 'getNetworkPools' (which might list all pools) or 'search' (which might have broader functionality). No exclusions or prerequisites are mentioned.

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