Skip to main content
Glama

getPoolDetails

Read-onlyIdempotent

Get the full current snapshot for one pool by address: its two tokens, current price, liquidity/TVL, 24h volume, and transaction counts, returned as a single pool object (not a list). Read-only and keyless. Use after search or getNetworkPools surfaces a pool, or for 'price/TVL of this pool?' or 'details for pool 0x...'. Returns live values only; for historical candles use getPoolOHLCV, and for the raw swap feed use getPoolTransactions. Params: network (required slug); pool_address (required, e.g. '0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640'); inversed (optional bool, default false, flips the token price ratio to token1/token0).

Input Schema

NameRequiredDescriptionDefault
networkYesREQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
inversedNoOPTIONAL: Whether to invert the price ratio (default: false)
rationaleYesREQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions` field for the full convention and worked examples.
pool_addressYesREQUIRED: Pool address or identifier (e.g., '0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640')

Output Schema

NameRequiredDescriptionDefault
idNo
feeNo
chainNo
dex_idNo
tokensNo
dex_nameNo
created_atNo
factory_idNo
last_priceNo
price_timeNo
price_statsNo
last_price_usdNo
token_reservesNo
created_at_block_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • changedOutput schema / properties / chain / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / created_at / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / created_at_block_number / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / dex_id / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / dex_name / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / factory_id / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / id / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / price_time / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / tokens / items / additionalProperties
      Removed value: -true
    • addedOutput schema / properties / tokens / items / anyOf
      Added value: +[
      +  {
      +    "additionalProperties": true,
      +    "properties": {
      +      "added_at": {
      +        "description": "ISO 8601 timestamp when DexPaprika first indexed this token.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "chain": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "decimals": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "fdv": {
      +        "description": "Fully-diluted valuation in USD.",
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "id": {
      +        "description": "Token contract address (chain-canonical form).",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "name": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "symbol": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / tokens / items / properties
      Removed value: -{
      -  "added_at": {
      -    "description": "ISO 8601 timestamp when DexPaprika first indexed this token.",
      -    "type": "string"
      -  },
      -  "chain": {
      -    "type": "string"
      -  },
      -  "decimals": {
      -    "type": "number"
      -  },
      -  "fdv": {
      -    "description": "Fully-diluted valuation in USD.",
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "id": {
      -    "description": "Token contract address (chain-canonical form).",
      -    "type": "string"
      -  },
      -  "name": {
      -    "type": "string"
      -  },
      -  "symbol": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / tokens / items / type
      Removed value: -"object"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "chain": {
      +      "type": "string"
      +    },
      +    "created_at": {
      +      "type": "string"
      +    },
      +    "created_at_block_number": {
      +      "type": "number"
      +    },
      +    "dex_id": {
      +      "type": "string"
      +    },
      +    "dex_name": {
      +      "type": "string"
      +    },
      +    "factory_id": {
      +      "type": "string"
      +    },
      +    "fee": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "last_price": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "last_price_usd": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "price_stats": {},
      +    "price_time": {
      +      "type": "string"
      +    },
      +    "token_reserves": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "tokens": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "added_at": {
      +            "description": "ISO 8601 timestamp when DexPaprika first indexed this token.",
      +            "type": "string"
      +          },
      +          "chain": {
      +            "type": "string"
      +          },
      +          "decimals": {
      +            "type": "number"
      +          },
      +          "fdv": {
      +            "description": "Fully-diluted valuation in USD.",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "description": "Token contract address (chain-canonical form).",
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "symbol": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description still adds real context beyond them: 'keyless' (no auth needed), 'Returns live values only' (no historical data), and 'a single pool object (not a list)' which sets the return shape expectation.

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?

Front-loaded with purpose and return contents, then usage, then exclusions, then params — a sensible order with no filler sentences. Dense but every clause carries information; the inline param recap is the only slightly redundant part given the schema.

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?

An output schema exists, so return values needn't be explained, yet the description still summarizes them briefly. Combined with the routing guidance to sibling tools and the explanation of the one non-obvious parameter, nothing an agent needs to call this correctly is missing.

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%, so baseline is 3. The description earns an extra point by explaining what 'inversed' actually does ('flips the token price ratio to token1/token0'), which is more concrete than the schema's 'Whether to invert the price ratio'. It omits the required 'rationale' parameter, but that is fully documented in the schema itself.

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?

Names a specific verb and resource ('Get the full current snapshot for one pool by address') and enumerates the returned fields, so an agent can distinguish it from list tools like getNetworkPools and time-series tools like getPoolOHLCV without opening the schema.

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?

Gives explicit trigger contexts ('after search or getNetworkPools surfaces a pool', 'price/TVL of this pool?') and names both alternatives for off-scope needs: getPoolOHLCV for historical candles and getPoolTransactions for the raw swap feed. When-to-use and when-not-to-use are both covered.

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.

Resources