Tapp Exchange MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Name | Description |
|---|---|
| tapp_get_poolsB | Get a paginated list of available pools on Tapp Exchange, optionally filtered by type and sorted by TVL |
| tapp_get_pool_infoC | Get detailed information about a specific pool by its ID |
| tapp_get_swap_estimateB | Estimate the amount received or needed for a swap on Tapp Exchange |
| tapp_get_swap_routeC | Get the optimal route information between two tokens |
| tapp_swap_ammC | Execute a swap on an AMM pool |
| tapp_swap_clmmC | Execute a swap on a CLMM (Concentrated Liquidity Market Maker) pool |
| tapp_swap_stableC | Execute a swap on a Stable pool |
| tapp_create_amm_pool_and_add_liquidityC | Create an AMM pool and add initial liquidity |
| tapp_create_clmm_pool_and_add_liquidityC | Create a CLMM pool and add initial liquidity |
| tapp_create_stable_pool_and_add_liquidityC | Create a Stable pool and add initial liquidity |
| tapp_add_amm_liquidityC | Add liquidity to an existing AMM pool |
| tapp_add_clmm_liquidityC | Add liquidity to an existing CLMM pool |
| tapp_add_stable_liquidityC | Add liquidity to an existing stable pool |
| tapp_remove_single_amm_liquidityC | Remove liquidity from a single AMM position |
| tapp_remove_multiple_amm_liquidityC | Remove liquidity from multiple AMM positions |
| tapp_remove_single_clmm_liquidityC | Remove liquidity from a single CLMM position |
| tapp_remove_multiple_clmm_liquidityC | Remove liquidity from multiple CLMM positions |
| tapp_remove_single_stable_liquidityC | Remove liquidity from a single STABLE position |
| tapp_remove_multiple_stable_liquidityC | Remove liquidity from multiple STABLE positions |
| tapp_get_positionsB | Get a paginated list of liquidity positions for a user address |
| tapp_collect_feeC | Collect fees from a specific liquidity position in a given pool |
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 21 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized by specific actions (add, create, get, remove, swap) and pool types (AMM, CLMM, Stable), making it easy to differentiate between them. For example, 'tapp_add_amm_liquidity' and 'tapp_swap_amm' target different operations on the same pool type, preventing misselection.
Tool names follow a highly consistent pattern throughout: all use snake_case with a 'tapp_' prefix, followed by a verb (e.g., add, create, get, remove, swap) and a noun phrase specifying the action and pool type. This predictability makes the set easy to navigate and understand at a glance.
With 21 tools, the count is slightly high but reasonable for a comprehensive DeFi exchange server covering multiple pool types and operations. It provides detailed coverage for AMM, CLMM, and Stable pools, though it might feel heavy compared to simpler servers. The tools are well-scoped, with each serving a specific function.
The tool surface offers complete CRUD/lifecycle coverage for liquidity management and swapping on Tapp Exchange. It includes creation, addition, removal, fee collection, information retrieval, and swapping for all pool types, with no obvious gaps. Agents can perform end-to-end operations without dead ends.