uniswap-poolspy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THEGRAPH_API_KEY | Yes | Your API key from The Graph |
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
| Name | Description |
|---|---|
| get_new_poolsB | Returns a list of trading pools created in the specified time range on Uniswap V3. Parameters: chain (str): The blockchain on which Uniswap is deployed. Default is 'ethereum'. Supported options include: 'ethereum', 'base', 'optimism', 'arbitrum', 'polygon', 'bsc', 'avalanche', 'celo' and 'blast'. order_by (str): The field to sort data in descending order before returning to the user. Default is 'timestamp'. Supported options include: - timestamp: Sort by Timestamp - txcount: Sort by Transaction Count - tvl: Sort by Total Value Locked - volume: Sort by Volume time_range_seconds (int): The time range in seconds to look back for new pools. Default is 300 seconds (5 minutes). limit (int): The maximum number of pools to return. Default is 100 pools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'get_new_pools' has a single, clearly defined purpose: retrieving newly created Uniswap V3 pools within a specified time range.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'get_new_pools' follows a clear verb_noun pattern (get + new_pools), which would be consistent if more tools were added.
A single tool is too few for a server named 'uniswap-poolspy-mcp', which suggests broader monitoring or analysis of Uniswap pools. This minimal toolset limits functionality to only retrieving new pools, lacking operations like querying existing pools, analyzing pool metrics, or tracking pool changes over time.
The tool surface is severely incomplete for the implied domain of Uniswap pool monitoring. While 'get_new_pools' covers discovery of new pools, there are significant gaps: no tools for getting pool details, tracking liquidity or volume trends, analyzing historical data, or performing CRUD-like operations on pool information, which agents would need for comprehensive analysis.