Skip to main content
Glama
tamago-labs

Tapp Exchange MCP Server

by tamago-labs

tapp_remove_single_stable_liquidity

Removes liquidity from a single STABLE pool 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 STABLE position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
poolIdYesThe ID of the stable pool
positionYesThe position object

Implementation Reference

  • Defines the MCP tool 'tapp_remove_single_stable_liquidity' including its Zod input schema and async handler function that delegates to TappAgent.removeSingleStableLiquidity.
    export const RemoveSingleStableLiquidityTool: McpTool = {
        name: "tapp_remove_single_stable_liquidity",
        description: "Remove liquidity from a single STABLE position",
        schema: {
            poolId: z.string().describe("The ID of the stable pool"),
            position: z.object({
                positionAddr: z.string().describe("The address of the individual liquidity position"),
                mintedShare: z.number().describe("The amount of share tokens to burn"),
                amounts: z.array(z.number()).describe("The minimum token amounts to receive")
            }).describe("The position object")
        },
        handler: async (agent: TappAgent, input: Record<string, any>) => {
            const result = await agent.removeSingleStableLiquidity({
                poolId: input.poolId,
                position: input.position
            });
            return {
                status: "success",
                transaction: result
            };
        },
    };
  • Zod schema defining the input parameters for the tool: poolId and position object with positionAddr, mintedShare, and amounts.
    schema: {
        poolId: z.string().describe("The ID of the stable pool"),
        position: z.object({
            positionAddr: z.string().describe("The address of the individual liquidity position"),
            mintedShare: z.number().describe("The amount of share tokens to burn"),
            amounts: z.array(z.number()).describe("The minimum token amounts to receive")
        }).describe("The position object")
    },
  • src/mcp/index.ts:48-53 (registration)
    Registers the RemoveSingleStableLiquidityTool in the TappExchangeMcpTools object export used for MCP server.
    "RemoveSingleAMMLiquidityTool": RemoveSingleAMMLiquidityTool,
    "RemoveMultipleAMMLiquidityTool": RemoveMultipleAMMLiquidityTool,
    "RemoveSingleCLMMLiquidityTool": RemoveSingleCLMMLiquidityTool,
    "RemoveMultipleCLMMLiquidityTool": RemoveMultipleCLMMLiquidityTool,
    "RemoveSingleStableLiquidityTool": RemoveSingleStableLiquidityTool,
    "RemoveMultipleStableLiquidityTool": RemoveMultipleStableLiquidityTool,
  • TappAgent helper method that calls the SDK to generate transaction payload for removing stable liquidity and submits it via Aptos client.
    async removeSingleStableLiquidity(params: RemoveSingleStableLiquidityParams): Promise<TransactionResponse> {
        try {
            const data = this.sdk.Position.removeSingleStableLiquidity(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'
            };
        }
    }
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 action without behavioral details. It doesn't disclose that this is a destructive/write operation (implied by 'Remove'), potential transaction costs, authorization needs, rate limits, or what happens to the removed liquidity (e.g., tokens returned to user). For a financial transaction tool, this is a significant gap in safety and operational context.

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 that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple action and front-loaded with the core verb and resource.

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 the complexity of a DeFi liquidity removal operation with no annotations and no output schema, the description is insufficient. It lacks critical context about transaction behavior, return values (what tokens are received), error conditions, or how this differs from sibling tools. For a tool that likely involves financial risk and blockchain interactions, more completeness is needed.

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 beyond the action name—it doesn't explain what 'poolId' or 'position' represent in context, or clarify the relationship between 'mintedShare' and 'amounts'. Baseline 3 is appropriate since 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 STABLE position'), which distinguishes it from other removal tools that handle AMM or CLMM positions. However, it doesn't explicitly differentiate from 'tapp_remove_multiple_stable_liquidity' beyond the 'single' vs 'multiple' naming, which is implied but not stated in the description itself.

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?

The description provides no guidance on when to use this tool versus alternatives like 'tapp_remove_multiple_stable_liquidity' or other liquidity removal tools. It doesn't mention prerequisites, such as needing an existing position, or contextual factors like gas costs or slippage considerations that might influence tool selection.

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