Skip to main content
Glama
tamago-labs

Tapp Exchange MCP Server

by tamago-labs

tapp_get_positions

Retrieve a paginated list of liquidity positions for a specific user address on Tapp Exchange, enabling efficient tracking of decentralized exchange activities on the Aptos blockchain.

Instructions

Get a paginated list of liquidity positions for a user address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoThe page number for pagination (defaults to 1)
sizeNoThe number of results per page (defaults to 10)
userAddrNoThe user's wallet address to fetch positions for (defaults to current agent address)

Implementation Reference

  • MCP tool handler for 'tapp_get_positions': calls TappAgent.getPositions with input params and returns formatted response with pagination info.
    handler: async (agent: TappAgent, input: Record<string, any>) => {
        const positions = await agent.getPositions({
            userAddr: input.userAddr,
            page: input.page || 1,
            size: input.size || 10
        });
        return {
            status: "success",
            positions,
            pagination: {
                page: input.page || 1,
                size: input.size || 10,
                total: positions.length
            }
        };
    },
  • Input schema validation using Zod for the tapp_get_positions tool parameters: userAddr (optional), page (optional), size (optional).
    schema: {
        userAddr: z.string().optional().describe("The user's wallet address to fetch positions for (defaults to current agent address)"),
        page: z.number().optional().describe("The page number for pagination (defaults to 1)"),
        size: z.number().optional().describe("The number of results per page (defaults to 10)")
    },
  • src/mcp/index.ts:56-56 (registration)
    Registration of the GetPositionsTool (tapp_get_positions) in the central TappExchangeMcpTools export object.
    "GetPositionsTool": GetPositionsTool,
  • src/mcp/index.ts:23-23 (registration)
    Import of GetPositionsTool from position-tools.ts for registration in MCP tools.
    import { GetPositionsTool, CollectFeeTool } from "./tapp/position-tools";
  • TappAgent.getPositions method called by the tool handler: resolves user address and delegates to SDK Position.getPositions.
    async getPositions(params: {
        userAddr?: string;
        page?: number;
        size?: number;
    }): Promise<TappPosition[]> {
        const userAddr = params.userAddr || await this.getAddress();
        const positions = await this.sdk.Position.getPositions({
            ...params,
            userAddr
        });
        return positions;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get a paginated list' implies a read-only operation, it doesn't specify authentication requirements, rate limits, error conditions, or what constitutes a 'liquidity position' in this context. The pagination behavior is mentioned but lacks details about maximum page sizes or total count availability.

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, well-structured sentence that efficiently conveys the core functionality. It's front-loaded with the main purpose and includes the key constraint (paginated) without unnecessary elaboration. Every word earns its place in this compact description.

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

Completeness3/5

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

For a read-only tool with 100% schema coverage but no output schema, the description adequately covers the basic operation. However, without annotations or output schema, it should ideally provide more context about what information the positions contain, how they're structured, or what the pagination response looks like to be fully complete.

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 fully documents all three parameters with their types, descriptions, and defaults. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline expectation but not providing extra value.

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 ('Get a paginated list') and resource ('liquidity positions for a user address'), making the purpose immediately understandable. However, it doesn't differentiate this read-only tool from its many sibling tools that involve adding, removing, or swapping liquidity, which would require explicit comparison to achieve a perfect score.

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 18 sibling tools including various pool creation, liquidity management, and swap operations, there's no indication whether this is for monitoring positions versus taking actions, or how it relates to tools like 'tapp_get_pool_info' or 'tapp_get_pools'.

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