uniswap_prices
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNISWAP_PRICES_RPC_URL | No | Override the Ethereum RPC endpoint. Default is https://ethereum-rpc.publicnode.com. | https://ethereum-rpc.publicnode.com |
| UNISWAP_PRICES_HTTP_HOST | No | Bind host for HTTP mode. Default is 127.0.0.1; Docker image sets to 0.0.0.0. | 127.0.0.1 |
| UNISWAP_PRICES_HTTP_PORT | No | Bind port for HTTP mode. Default is 8000. | 8000 |
| UNISWAP_PRICES_TRANSPORT | No | Transport mode: 'stdio' (default) or 'http'. | stdio |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_v1_reservesA | Reads the on-chain ETH/token reserves of a token's Uniswap V1 exchange. Uniswap V1 pairs are always ETH<->token. |
| get_v2_reservesA | Reads the on-chain reserves of a Uniswap V2 pair via getReserves().
|
| get_v3_reservesA | Reads the on-chain reserves (pool token balances) of Uniswap V3 pool(s).
|
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 3 tools
Each tool targets a distinct Uniswap version with explicit version-specific parameters (V1 token, V2 token_a/token_b, V3 fee tiers), so there is no ambiguity. Names and descriptions clearly signal which contract type is accessed.
All three tools follow an identical get_v{version}_reserves pattern, making the API predictable and easy to navigate. No mixed casing or inconsistent verbs are present.
Three tools map cleanly to the three major Uniswap versions, and each serves a distinct endpoint type. The count is well-scoped for a narrow read-only reserves server.
The set covers all three Uniswap versions but only exposes raw reserves; V1/V2 reserves are sufficient to compute prices, while V3 prices require sqrtPriceX96 which is not provided. A direct current-price or quote tool would close this notable gap.