Skip to main content
Glama
kukapay

liquidity-pools-mcp

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_liquidity_poolsA
Fetch all liquidity pools for a given chain ID and token address from DexScreener API.

Args:
    chain_id (str): The blockchain identifier (e.g., 'bsc' for Binance Smart Chain, 'eth' for Ethereum)
    token_address (str): The contract address of the token (e.g., '0xe6DF05CE8C8301223373CF5B969AFCb1498c5528')
    ctx (Context): MCP context for logging and request handling

Returns:
    str: A markdown table containing liquidity pool details including dexId, pairAddress, 
         base/quote token symbols, price USD, 24h buy/sell transactions, 24h volume, 
         liquidity USD, and market cap, followed by total liquidity USD

Prompts

Interactive templates invoked by user choice

NameDescription
liquidity_pool_queryGenerate a prompt for querying liquidity pools

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool has a single, clearly defined purpose of fetching liquidity pools from DexScreener API.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern (get_liquidity_pools), which is consistent within this minimal set. There are no other tools to create inconsistency.

Tool Count2/5

A single tool is too few for a server focused on liquidity pools, which typically involves operations like creating, updating, or analyzing pools beyond just fetching. This feels incomplete for the domain.

Completeness2/5

The tool surface is severely incomplete for liquidity pool management. It only provides a fetch operation (get), missing essential CRUD operations like create, update, or delete pools, as well as analytical tools for deeper insights.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources