Skip to main content
Glama

getPoolTransactions

Retrieve recent swap, add, and remove transactions for a specific liquidity pool on supported blockchains to monitor trading activity and analyze pool dynamics.

Instructions

Get recent transactions for a specific pool. Shows swaps, adds, removes. Requires network and pool address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkYesNetwork ID from getNetworks (e.g., "ethereum", "solana")
poolAddressYesPool address or identifier
pageNoPage number for pagination (up to 100 pages)
limitNoNumber of items per page (max 100)
cursorNoTransaction ID used for cursor-based pagination

Implementation Reference

  • The handler function for the getPoolTransactions tool. It constructs an API endpoint based on the input parameters (network, poolAddress, page, limit, cursor) and fetches transaction data using fetchFromAPI, then formats it with formatMcpResponse.
    async ({ network, poolAddress, page, limit, cursor }) => {
      let endpoint = `/networks/${network}/pools/${poolAddress}/transactions?page=${page}&limit=${limit}`;
      if (cursor) {
        endpoint += `&cursor=${encodeURIComponent(cursor)}`;
      }
      const data = await fetchFromAPI(endpoint);
      return formatMcpResponse(data);
    }
  • The input schema for the getPoolTransactions tool, defined using Zod (z.object implied), with parameters for network, poolAddress, page, limit, and optional cursor.
    {
      network: z.string().describe('Network ID from getNetworks (e.g., "ethereum", "solana")'),
      poolAddress: z.string().describe('Pool address or identifier'),
      page: z.number().optional().default(0).describe('Page number for pagination (up to 100 pages)'),
      limit: z.number().optional().default(10).describe('Number of items per page (max 100)'),
      cursor: z.string().optional().describe('Transaction ID used for cursor-based pagination')
    },
  • src/index.js:212-230 (registration)
    The registration of the getPoolTransactions tool using server.tool(), including the tool name, description, input schema, and inline handler function.
    server.tool(
      'getPoolTransactions',
      'Get recent transactions for a specific pool. Shows swaps, adds, removes. Requires network and pool address.',
      {
        network: z.string().describe('Network ID from getNetworks (e.g., "ethereum", "solana")'),
        poolAddress: z.string().describe('Pool address or identifier'),
        page: z.number().optional().default(0).describe('Page number for pagination (up to 100 pages)'),
        limit: z.number().optional().default(10).describe('Number of items per page (max 100)'),
        cursor: z.string().optional().describe('Transaction ID used for cursor-based pagination')
      },
      async ({ network, poolAddress, page, limit, cursor }) => {
        let endpoint = `/networks/${network}/pools/${poolAddress}/transactions?page=${page}&limit=${limit}`;
        if (cursor) {
          endpoint += `&cursor=${encodeURIComponent(cursor)}`;
        }
        const data = await fetchFromAPI(endpoint);
        return formatMcpResponse(data);
      }
    );
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 mentions required parameters but doesn't disclose key behavioral traits: it doesn't specify if this is a read-only operation (implied by 'Get' but not explicit), what the output format looks like (critical with no output schema), rate limits, authentication needs, or error conditions. The description adds minimal context beyond basic functionality.

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 two sentences, front-loaded with core purpose and followed by prerequisites. Every word earns its place: 'Get recent transactions for a specific pool' establishes the action, 'Shows swaps, adds, removes' clarifies scope, and 'Requires network and pool address' states needs. No wasted verbiage.

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 no annotations and no output schema, the description is incomplete for a tool with 5 parameters and complex behavior (transaction listing with pagination). It lacks details on return values, error handling, rate limits, and how transactions are filtered or sorted. For a read operation with pagination and no structured output, more context is needed to guide the agent effectively.

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 5 parameters thoroughly. The description adds marginal value by noting that network and pool address are required, but doesn't provide additional meaning beyond what's in the schema (e.g., explaining transaction types further or pagination behavior). Baseline 3 is appropriate when schema does 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 verb ('Get') and resource ('recent transactions for a specific pool'), specifying the types of transactions included (swaps, adds, removes). It distinguishes from siblings like getPoolDetails or getPoolOHLCV by focusing on transaction history rather than pool metadata or price data. However, it doesn't explicitly contrast with all siblings (e.g., search might also return transactions).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by stating 'Requires network and pool address,' indicating prerequisites. It doesn't provide explicit when-to-use vs. when-not-to-use guidance or name specific alternatives among siblings. The agent must infer that this is for transaction history of a known pool, while getDexPools or getNetworkPools might be for discovery.

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

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/infinity-smithpl/dexpaprika-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server