Skip to main content
Glama
tamago-labs

Tapp Exchange MCP Server

by tamago-labs

tapp_swap_amm

Use this tool to execute token swaps on Automated Market Maker (AMM) pools on the Aptos blockchain. Specify pool address, swap direction, and token amounts to trade assets efficiently.

Instructions

Execute a swap on an AMM pool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
a2bYesDirection of the swap; true for token A to B, false for B to A
amount0YesAmount of token A
amount1YesAmount of token B
fixedAmountInNoWhether the input amount is fixed (defaults to true)
poolIdYesThe address of the pool in which the swap is performed

Implementation Reference

  • The MCP tool handler function for 'tapp_swap_amm' that validates input, calls TappAgent.swapAMM, and returns the transaction result.
    handler: async (agent: TappAgent, input: Record<string, any>) => {
        const result = await agent.swapAMM({
            poolId: input.poolId,
            a2b: input.a2b,
            fixedAmountIn: input.fixedAmountIn ?? true,
            amount0: input.amount0,
            amount1: input.amount1
        });
        return {
            status: "success",
            transaction: result
        };
    },
  • Zod schema defining the input parameters for the tapp_swap_amm tool.
    schema: {
        poolId: z.string().describe("The address of the pool in which the swap is performed"),
        a2b: z.boolean().describe("Direction of the swap; true for token A to B, false for B to A"),
        fixedAmountIn: z.boolean().optional().describe("Whether the input amount is fixed (defaults to true)"),
        amount0: z.number().describe("Amount of token A"),
        amount1: z.number().describe("Amount of token B")
    },
  • src/mcp/index.ts:33-33 (registration)
    Registration of the SwapAMMTool (tapp_swap_amm) in the central MCP tools export.
    "SwapAMMTool": SwapAMMTool,
  • TappAgent.swapAMM helper method that generates the swap transaction payload using the Tapp SDK and submits it via Aptos client.
    async swapAMM(params: SwapAMMParams): Promise<TransactionResponse> {
        try {
            const data = this.sdk.Swap.swapAMMTransactionPayload(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 for behavioral disclosure. While 'Execute a swap' implies a write/mutation operation, the description doesn't disclose critical behavioral aspects like authentication requirements, rate limits, whether the swap is atomic/irreversible, gas costs, slippage considerations, or what happens on failure. This leaves significant gaps for a financial transaction tool.

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 appropriately sized for a tool with good schema documentation and gets straight to the point without unnecessary elaboration.

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?

For a financial swap operation with no annotations and no output schema, the description is incomplete. It doesn't address critical context like transaction outcomes, error conditions, return values, or how this differs from other swap tools. The combination of a mutation tool with zero annotation coverage and minimal description creates significant gaps for safe and effective use.

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 all parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters (e.g., how amount0 and amount1 interact with a2b and fixedAmountIn) or provide 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 ('Execute a swap') and the resource ('on an AMM pool'), which is specific and unambiguous. However, it doesn't explicitly differentiate this tool from its siblings like 'tapp_swap_clmm' or 'tapp_swap_stable', which appear to be alternative swap implementations for different pool types.

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. With multiple sibling tools for different swap types (AMM, CLMM, stable) and related tools like 'tapp_get_swap_estimate' or 'tapp_get_swap_route', there's no indication of when this specific AMM swap is appropriate versus other swap methods or preparatory 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