Skip to main content
Glama

DeFade — Multi-Chain Memecoin Analyzer

Liquidity analysis

get_liquidity
Read-onlyIdempotent

Liquidity pool analysis for one token: which DEX holds the deepest pool, its depth in USD, and whether the LP tokens are burned, locked or still in someone's hands. lpStatus is the verdict — LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, LP MULTI-PROVIDER (a pool with no LP token whose positions are split between independent providers, none holding a fifth of the liquidity), BONDING CURVE (still on a launchpad curve, no pool yet) or NO LP FOUND, with combinations spelled out — and lpBurnPct, lpLockPct, poolLocks and positionLock carry the evidence. Use it to answer whether liquidity is locked, how deep it is, and whether the position could be pulled: LP UNLOCKED means it can be pulled at any time. Cached for about two minutes. A token with no pool returns empty liquidity data, which is itself a warning on a token that is trading. Not for price or volume (get_token_price), market cap (get_token_scan) or holder concentration (get_holders). Arguments: address and chain — pools live per chain, so a 0x address needs the chain it trades on, and a Base pool is not found under ethereum; one API unit on any chain.

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": "get_liquidity"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm, monad, elysium. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan.solana
addressYesThe token's own contract address, exactly as an explorer shows it. Solana: the base58 mint, 32-44 characters (e.g. 6p6xgHyF7AeE6TZkSmFsko444wqoP15icUSqi2jfGiPN). EVM: 0x followed by 40 hex characters, case-insensitive (e.g. 0x6982508145454ce325ddbe47a25d4ec3d2311933). Never a pool, pair, wallet or deployer address — those come back as not found. Set `chain` to match the address: a 0x address alone cannot say which EVM chain it lives on, and a Solana mint sent with an EVM chain is rejected.

Output Schema

NameRequiredDescriptionDefault
dexNoWhich DEX holds the deepest pool.
riskNoLiquidity risk label; lpEvidence carries the on-chain evidence behind it.
tokenNoThe address that was scanned (on get_token_scan, the full token metadata object instead).
lpStatusNoHeadline pool verdict: LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, LP MULTI-PROVIDER (no LP token, and its positions are split between independent providers, none holding a fifth of the liquidity), LP HELD BY DAO (a MetaDAO token: the vault of its DAO holds the liquidity), BONDING CURVE, NO LP FOUND, or a spelled-out combination.
lpBurnPctNoPercent of LP tokens burned; lpLockPct is the percent locked.
poolLocksNoPer-pool lock detail with lpLockable and an lpNote in words.
poweredByNoAlways "DeFade.org".
timestampNoISO time the response was assembled.
positionLockNoA main pool with no LP token (Solana: Orca, Meteora DLMM, Raydium CLMM; EVM: v3/v4): who holds its positions, read on chain. largestOpenOwner (address, pct) is the largest single provider's share of ALL the liquidity; lockedPct, burnedPct and unknownPct (not read) are shares of it too; on Solana creator (address, pct) is the creator's share and perPool the pools read. Null when the main pool has an LP token.
totalLiquidityUsdNoCombined USD depth across pools; pools lists them and poolCount counts them. On an EVM chain, null when the pair feed gives no pool a liquidity figure, or the reserve of a bonding curve could not be priced: unknown, not zero.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm, monad. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."New value: +"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm, monad, elysium. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "solana",
      -  "ethereum",
      -  "base",
      -  "bsc",
      -  "robinhood",
      -  "arc",
      -  "hyperevm",
      -  "monad"
      -]New value: +[
      +  "solana",
      +  "ethereum",
      +  "base",
      +  "bsc",
      +  "robinhood",
      +  "arc",
      +  "hyperevm",
      +  "monad",
      +  "elysium"
      +]
  2. Changed2 schema fields changed
    • changedOutput schema / properties / lpStatus / description
      Previous value: -"Headline pool verdict: LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, LP HELD BY DAO (a MetaDAO token: the vault of its DAO holds the liquidity), BONDING CURVE, NO LP FOUND, or a spelled-out combination."New value: +"Headline pool verdict: LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, LP MULTI-PROVIDER (no LP token, and its positions are split between independent providers, none holding a fifth of the liquidity), LP HELD BY DAO (a MetaDAO token: the vault of its DAO holds the liquidity), BONDING CURVE, NO LP FOUND, or a spelled-out combination."
    • addedOutput schema / properties / positionLock
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "A main pool with no LP token (Solana: Orca, Meteora DLMM, Raydium CLMM; EVM: v3/v4): who holds its positions, read on chain. largestOpenOwner (address, pct) is the largest single provider's share of ALL the liquidity; lockedPct, burnedPct and unknownPct (not read) are shares of it too; on Solana creator (address, pct) is the creator's share and perPool the pools read. Null when the main pool has an LP token.",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  3. Changed1 schema field changed
    • changedOutput schema / properties / totalLiquidityUsd / description
      Previous value: -"Combined USD depth across pools; pools lists them and poolCount counts them."New value: +"Combined USD depth across pools; pools lists them and poolCount counts them. On an EVM chain, null when the pair feed gives no pool a liquidity figure, or the reserve of a bonding curve could not be priced: unknown, not zero."
  4. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."New value: +"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm, monad. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "solana",
      -  "ethereum",
      -  "base",
      -  "bsc",
      -  "robinhood",
      -  "arc",
      -  "hyperevm"
      -]New value: +[
      +  "solana",
      +  "ethereum",
      +  "base",
      +  "bsc",
      +  "robinhood",
      +  "arc",
      +  "hyperevm",
      +  "monad"
      +]
  5. Changed1 schema field changed
    • changedOutput schema / properties / lpStatus / description
      Previous value: -"Headline pool verdict: LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, BONDING CURVE, NO LP FOUND, or a spelled-out combination."New value: +"Headline pool verdict: LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, LP HELD BY DAO (a MetaDAO token: the vault of its DAO holds the liquidity), BONDING CURVE, NO LP FOUND, or a spelled-out combination."
  6. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"Chain the token is deployed on: solana (default), ethereum, base, robinhood. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."New value: +"Chain the token is deployed on: solana (default), ethereum, base, bsc, robinhood, arc, hyperevm. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "solana",
      -  "ethereum",
      -  "base",
      -  "robinhood"
      -]New value: +[
      +  "solana",
      +  "ethereum",
      +  "base",
      +  "bsc",
      +  "robinhood",
      +  "arc",
      +  "hyperevm"
      +]
  7. Changed1 schema field changed
    • changedOutput schema / properties / lpStatus / description
      Previous value: -"Headline pool verdict: BURNED, LOCKED, UNLOCKED, NO LP FOUND."New value: +"Headline pool verdict: LP BURNED, LP LOCKED, LP UNLOCKED, PARTIALLY BURNED, LP NOT LOCKABLE, BONDING CURVE, NO LP FOUND, or a spelled-out combination."
  8. Changed8 schema fields changed
    • changedOutput schema / properties / dex / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / lpBurnPct / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / lpStatus / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / poolLocks / type
      Previous value: -"array"New value: +[
      +  "array",
      +  "null"
      +]
    • changedOutput schema / properties / poweredBy / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / risk / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / timestamp / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / totalLiquidityUsd / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
  9. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "dex": {
      +      "description": "Which DEX holds the deepest pool.",
      +      "type": "string"
      +    },
      +    "lpBurnPct": {
      +      "description": "Percent of LP tokens burned; lpLockPct is the percent locked.",
      +      "type": "number"
      +    },
      +    "lpStatus": {
      +      "description": "Headline pool verdict: BURNED, LOCKED, UNLOCKED, NO LP FOUND.",
      +      "type": "string"
      +    },
      +    "poolLocks": {
      +      "description": "Per-pool lock detail with lpLockable and an lpNote in words.",
      +      "type": "array"
      +    },
      +    "poweredBy": {
      +      "description": "Always \"DeFade.org\".",
      +      "type": "string"
      +    },
      +    "risk": {
      +      "description": "Liquidity risk label; lpEvidence carries the on-chain evidence behind it.",
      +      "type": "string"
      +    },
      +    "timestamp": {
      +      "description": "ISO time the response was assembled.",
      +      "type": "string"
      +    },
      +    "token": {
      +      "description": "The address that was scanned (on get_token_scan, the full token metadata object instead)."
      +    },
      +    "totalLiquidityUsd": {
      +      "description": "Combined USD depth across pools; pools lists them and poolCount counts them.",
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  10. Changed2 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"Token contract address. A base58 mint for Solana, or 0x-prefixed for EVM chains. Set `chain` to match — a 0x address alone cannot say which EVM chain it lives on."New value: +"The token's own contract address, exactly as an explorer shows it. Solana: the base58 mint, 32-44 characters (e.g. 6p6xgHyF7AeE6TZkSmFsko444wqoP15icUSqi2jfGiPN). EVM: 0x followed by 40 hex characters, case-insensitive (e.g. 0x6982508145454ce325ddbe47a25d4ec3d2311933). Never a pool, pair, wallet or deployer address — those come back as not found. Set `chain` to match the address: a 0x address alone cannot say which EVM chain it lives on, and a Solana mint sent with an EVM chain is rejected."
    • changedInput schema / properties / chain / description
      Previous value: -"Which chain the address lives on. Defaults to solana."New value: +"Chain the token is deployed on: solana (default), ethereum, base, robinhood. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."
  11. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description still adds real value beyond them: a ~2 minute cache window, the meaning of each lpStatus verdict including LP UNLOCKED meaning the position can be pulled at any time, and the empty-result semantics. What it omits is response shape and failure behavior, which keeps it at a solid 3 rather than higher.

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?

Purpose and the sibling exclusions are front-loaded, and there is no filler or marketing language. The middle section is a long run-on enumeration of eight lpStatus values that is information-dense but harder to scan than a list would be, which is the only structural weakness.

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?

With an output schema present, the description need not restate return structure, yet it goes further by decoding the lpStatus verdict vocabulary and the evidence fields that support it. Chain-dependent lookup behavior, caching, cost, and empty-result handling are all covered for a two-parameter read tool.

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 the schema already documents both parameters thoroughly, including the 0x-address-needs-chain rule and enum values. The description reinforces the chain/address coupling with a concrete failure case ("a Base pool is not found under ethereum") and adds genuinely new cost information ("one API unit on any chain") that the schema does not state.

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 first sentence names a specific verb and resource — liquidity pool analysis for one token — and immediately enumerates the three things returned (deepest DEX, USD depth, LP token custody). It then explicitly rules out siblings: "Not for price or volume (get_token_price), market cap (get_token_scan) or holder concentration (get_holders)."

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?

Usage is stated directly: "Use it to answer whether liquidity is locked, how deep it is, and whether the position could be pulled." It names three alternative tools and the questions they own instead, plus the interpretation rule that an empty result on a trading token is itself a warning.

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