Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Liquidity pool check: a Base DEX pair's liquidity, volume, trades and age before trading

liquidity_pool_audit
Read-only

Check a Base DEX pool before you trade: give a pair address and get the verified DEX, both tokens, reported liquidity, 24h volume and trades, and pair age from DexScreener, or read on Base when it is unavailable, with source and retrieval time. Missing fields are null; an unknown pair returns 422. Market data only, no risk assessment. Use to confirm a pair is real and deep enough before trading; token red flags: token_report. Example: address=0x98c7A2338336d2d354663246F64676009c7bDa97. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "liquidity_pool_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesDEX pair address on Base, 0x-prefixed 20-byte hex

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover safety (readOnly/destructive) and open-world behavior, and the description goes well beyond them: it discloses the primary source and the fallback ('or read on Base when it is unavailable'), that source and retrieval time are returned, that missing fields are null, that an unknown pair returns 422, and the pricing model including 'failed calls free'. It also explains why the operation is not idempotent in practice — 'each call is charged, so repeats are not free'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and usage clause is front-loaded and nothing is filler; every sentence carries operational information. It is dense and semicolon-chained, and the charging model is stated twice in slightly different forms, which costs a little crispness.

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

Completeness5/5

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

For a one-parameter read tool with no output schema, the description fully specifies inputs, the returned field set, error behavior (422), data provenance and freshness, and cost. An agent could call this correctly with no further information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single parameter, so the schema already defines format ('0x-prefixed 20-byte hex'); the description's marginal contribution is a concrete worked example address. That is useful for format confirmation but adds little beyond the structured field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (check a Base DEX pool by pair address) and enumerates the exact return fields: verified DEX, both tokens, reported liquidity, 24h volume/trades, and pair age. It also explicitly separates itself from token_report by scope ('Market data only, no risk assessment').

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

Usage Guidelines5/5

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

It states the decision context directly ('Use to confirm a pair is real and deep enough before trading') and routes the adjacent need elsewhere ('token red flags: token_report'). It also declares an exclusion — no risk assessment — so the agent knows when not to rely on it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.