Skip to main content
Glama
tamago-labs

Tapp Exchange MCP Server

by tamago-labs

tapp_get_pool_info

Retrieve detailed information about a specific liquidity pool by providing its ID, using the tool from Tapp Exchange MCP Server to support pool management and trading operations.

Instructions

Get detailed information about a specific pool by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
poolIdYesThe pool ID to get information for

Implementation Reference

  • The handler function for the 'tapp_get_pool_info' MCP tool, which retrieves pool information via the TappAgent and returns formatted response.
    handler: async (agent: TappAgent, input: Record<string, any>) => {
        const poolInfo = await agent.getPoolInfo(input.poolId);
        return {
            status: "success",
            pool: poolInfo
        };
    },
  • Zod schema defining the input parameter 'poolId' for the tool.
    schema: {
        poolId: z.string().describe("The pool ID to get information for")
    },
  • src/mcp/index.ts:28-28 (registration)
    Registration of the GetPoolInfoTool in the central TappExchangeMcpTools object.
    "GetPoolInfoTool": GetPoolInfoTool,
  • src/index.ts:20-52 (registration)
    Dynamic MCP server.tool() registration loop that registers 'tapp_get_pool_info' using its name, description, schema, and wrapped handler.
    for (const [_key, tool] of Object.entries(TappExchangeMcpTools)) {
        server.tool(tool.name, tool.description, tool.schema, async (params: any): Promise<any> => {
            try {
                // Execute the handler with the params directly
                const result = await tool.handler(agent, params);
    
                // Format the result as MCP tool response
                return {
                    content: [
                        {
                            type: "text",
                            text: JSON.stringify(result, null, 2),
                        },
                    ],
                };
            } catch (error) {
                console.error("error", error);
                // Handle errors in MCP format
                return {
                    isError: true,
                    content: [
                        {
                            type: "text",
                            text:
                                error instanceof Error
                                    ? error.message
                                    : "Unknown error occurred",
                        },
                    ],
                };
            }
        })
    }
  • TappAgent helper method called by the tool handler to fetch pool info from the SDK.
    async getPoolInfo(poolId: string): Promise<TappPool> {
        const info = await this.sdk.Pool.getInfo(poolId);
        return info;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets' information, implying a read-only operation, but does not specify aspects like authentication needs, rate limits, error handling, or what 'detailed information' entails, leaving significant gaps in behavioral 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, direct sentence with no wasted words, efficiently conveying the core action and resource. It is appropriately sized and front-loaded, 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 implied by sibling tools (e.g., liquidity management, swaps) and the lack of annotations and output schema, the description is insufficient. It does not explain what 'detailed information' includes, potential return values, or operational constraints, making it incomplete for effective tool use in this context.

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?

The input schema has 100% description coverage, with the parameter 'poolId' documented as 'The pool ID to get information for'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without enhancing parameter understanding.

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 verb ('Get') and resource ('detailed information about a specific pool'), making the purpose evident. However, it does not explicitly differentiate from its sibling 'tapp_get_pools', which likely lists multiple pools, leaving some ambiguity in sibling distinction.

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, such as 'tapp_get_pools' for listing pools or other tools for pool operations. It lacks context on prerequisites or exclusions, offering minimal usage direction.

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