Skip to main content
Glama
lordbasilaiassistant-sudo

base-flash-arb-mcp

get_pool_reserves

Retrieve liquidity reserves for a token across all DEX pools on Base to analyze arbitrage opportunities and price gaps.

Instructions

Get reserves/liquidity for a token across all known DEX pools on Base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
token_addressYesToken contract address on Base

Implementation Reference

  • The handler function for the `get_pool_reserves` tool, which fetches pool liquidity information for a given token address.
    // Tool 2: get_pool_reserves
    server.tool(
      "get_pool_reserves",
      "Get reserves/liquidity for a token across all known DEX pools on Base.",
      {
        token_address: z.string().describe("Token contract address on Base"),
      },
      async ({ token_address }) => {
        try {
          const symbol = await getSymbol(token_address);
          const pools = await getAllPools(token_address);
    
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(
                  {
                    token: token_address,
                    symbol,
                    poolsFound: pools.length,
                    pools,
                  },
                  null,
                  2
                ),
              },
            ],
          };
        } catch (e) {
          return {
            content: [
              {
                type: "text" as const,
                text: `Error fetching pools: ${e instanceof Error ? e.message : String(e)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but lacks critical details: it doesn't specify if this is a read-only operation, what the output format looks like (e.g., list of pools with reserves), whether it requires authentication, rate limits, or how it handles errors. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 that front-loads the core purpose without unnecessary words. Every part of the sentence contributes directly to understanding the tool's function, making it highly concise and well-structured.

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 lack of annotations and output schema, the description is incomplete for a tool that likely returns complex data (reserves across multiple DEX pools). It doesn't cover behavioral aspects like safety, output structure, or error handling, which are essential for an AI agent to use it correctly in a blockchain 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 description implies the parameter 'token_address' is used to identify the token, but adds no semantic details beyond what the schema provides (which has 100% coverage with a clear description). It doesn't explain format requirements (e.g., checksummed address), validation rules, or examples, so it meets the baseline for high schema coverage without adding 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 reserves/liquidity') and target resource ('for a token across all known DEX pools on Base'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'get_price_across_dexes' or 'scan_top_tokens', which might also involve token data across DEXes.

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. It doesn't mention prerequisites, exclusions, or compare it to siblings such as 'get_price_across_dexes' (which might return price data rather than reserves) or 'scan_top_tokens' (which might scan multiple tokens rather than a specific one).

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/lordbasilaiassistant-sudo/base-flash-arb-mcp'

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