Skip to main content
Glama
tamago-labs

Tapp Exchange MCP Server

by tamago-labs

tapp_remove_single_clmm_liquidity

Remove liquidity from a single CLMM position on Tapp Exchange. Specify the pool ID, position address, share tokens to burn, and minimum token amounts to withdraw.

Instructions

Remove liquidity from a single CLMM position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
minAmount0YesMinimum amount of token0
minAmount1YesMinimum amount of token1
mintedShareYesThe amount of share tokens to burn
poolIdYesThe ID of the CLMM pool
positionAddrYesThe address of the liquidity position

Implementation Reference

  • MCP tool handler that validates input, calls TappAgent.removeSingleCLMMLiquidity, and returns transaction result.
    handler: async (agent: TappAgent, input: Record<string, any>) => {
        const result = await agent.removeSingleCLMMLiquidity({
            poolId: input.poolId,
            positionAddr: input.positionAddr,
            mintedShare: input.mintedShare,
            minAmount0: input.minAmount0,
            minAmount1: input.minAmount1
        });
        return {
            status: "success",
            transaction: result
        };
    },
  • Zod input schema defining parameters for removing single CLMM liquidity.
    schema: {
        poolId: z.string().describe("The ID of the CLMM pool"),
        positionAddr: z.string().describe("The address of the liquidity position"),
        mintedShare: z.number().describe("The amount of share tokens to burn"),
        minAmount0: z.number().describe("Minimum amount of token0"),
        minAmount1: z.number().describe("Minimum amount of token1")
    },
  • src/mcp/index.ts:50-50 (registration)
    Registration of the tool in the main TappExchangeMcpTools object.
    "RemoveSingleCLMMLiquidityTool": RemoveSingleCLMMLiquidityTool,
  • TappAgent helper method that uses the Tapp SDK to generate transaction payload and submits it via Aptos client.
    async removeSingleCLMMLiquidity(params: RemoveSingleCLMMLiquidityParams): Promise<TransactionResponse> {
        try {
            const data = this.sdk.Position.removeSingleCLMMLiquidity(params);
            const response = await this.aptos.transaction.submit.simple({
                sender: this.account.accountAddress,
                data: data
            } as any);
    
            return {
                hash: response.hash,
                success: true
            };
        } catch (error) {
            return {
                hash: '',
                success: false,
                error: error instanceof Error ? error.message : 'Unknown error'
            };
        }
    }
  • src/mcp/index.ts:10-22 (registration)
    Import of the RemoveSingleCLMMLiquidityTool from liquidity-tools.ts for registration.
        CreateAMMPoolAndAddLiquidityTool,
        CreateCLMMPoolAndAddLiquidityTool,
        CreateStablePoolAndAddLiquidityTool,
        AddAMMLiquidityTool,
        AddCLMMLiquidityTool,
        AddStableLiquidityTool,
        RemoveSingleAMMLiquidityTool,
        RemoveMultipleAMMLiquidityTool,
        RemoveSingleCLMMLiquidityTool,
        RemoveMultipleCLMMLiquidityTool,
        RemoveSingleStableLiquidityTool,
        RemoveMultipleStableLiquidityTool
    } from "./tapp/liquidity-tools";
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose critical behavioral traits such as whether this is a destructive operation (likely yes, given 'remove'), what permissions or authentication are needed, potential rate limits, or what happens to the removed liquidity (e.g., returned to user wallet).

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete for a tool that performs a likely destructive financial operation. It lacks information on behavioral context, error conditions, return values, and differentiation from sibling tools, leaving significant gaps for an AI agent to understand proper usage.

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%, so parameters are well-documented in the schema itself. The description adds no additional meaning about parameters beyond implying they relate to a 'single CLMM position', which aligns with schema fields like 'positionAddr'. Baseline 3 is appropriate as the schema does the heavy lifting.

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 action ('Remove liquidity') and specifies the resource type ('from a single CLMM position'), which distinguishes it from stable or AMM variants. However, it doesn't explicitly differentiate from 'tapp_remove_multiple_clmm_liquidity' or explain what 'single' means operationally.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'tapp_remove_multiple_clmm_liquidity' or 'tapp_remove_single_amm_liquidity'. The description mentions 'single' but doesn't clarify whether this refers to removing from one position versus multiple positions or other contextual differences.

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

Related 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/tamago-labs/tapp-exchange-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server