Skip to main content
Glama
tamago-labs

Tapp Exchange MCP Server

by tamago-labs

tapp_remove_multiple_stable_liquidity

Remove liquidity from multiple stable pool positions on Tapp Exchange. Specify pool ID, position addresses, share tokens to burn, and minimum token amounts to receive for efficient withdrawal.

Instructions

Remove liquidity from multiple STABLE positions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
poolIdYesThe ID of the stable pool
positionsYesAn array of position objects

Implementation Reference

  • The handler function for the 'tapp_remove_multiple_stable_liquidity' MCP tool, which delegates to the TappAgent's removeMultipleStableLiquidity method and formats the response.
    handler: async (agent: TappAgent, input: Record<string, any>) => {
        const result = await agent.removeMultipleStableLiquidity({
            poolId: input.poolId,
            positions: input.positions
        });
        return {
            status: "success",
            transaction: result
        };
    },
  • Zod input schema defining the parameters: poolId and array of positions with positionAddr, mintedShare, and amounts.
    schema: {
        poolId: z.string().describe("The ID of the stable pool"),
        positions: z.array(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("An array of position objects")
    },
  • src/mcp/index.ts:53-53 (registration)
    Registration of the tool object in the central TappExchangeMcpTools export under the key 'RemoveMultipleStableLiquidityTool'.
    "RemoveMultipleStableLiquidityTool": RemoveMultipleStableLiquidityTool,
  • TappAgent helper method that uses the external SDK to generate transaction payload for removing multiple stable liquidity and submits it via Aptos client.
    async removeMultipleStableLiquidity(params: RemoveMultipleStableLiquidityParams): Promise<TransactionResponse> {
        try {
            const data = this.sdk.Position.removeMultipleStableLiquidity(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?

No annotations are provided, so the description carries full burden. It states the action ('Remove liquidity') but doesn't disclose critical behavioral traits such as whether this is a destructive/write operation, permission requirements, transaction implications, gas costs, or error conditions. For a financial operation with no annotation coverage, this is a significant gap.

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 waste. 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 the complexity of a financial liquidity removal operation with no annotations and no output schema, the description is incomplete. It lacks information on behavioral aspects, return values, error handling, 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 the schema already documents both parameters (poolId and positions array with nested objects). The description adds no additional meaning beyond what's in the schema—it doesn't explain parameter relationships, constraints, or practical usage examples. Baseline 3 is appropriate when 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 ('multiple STABLE positions'), which distinguishes it from single-position removal tools. However, it doesn't explicitly differentiate from other 'remove_multiple' tools for different pool types (AMM/CLMM), though the 'STABLE' qualifier helps.

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_single_stable_liquidity or other pool-type removal tools. The description lacks context about prerequisites, timing, or comparison with sibling tools.

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