Skip to main content
Glama

DeFade — Multi-Chain Memecoin Analyzer

by org.defade
OverviewDiscussionsAdmin

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, BONDING CURVE (still on a launchpad curve, no pool yet) or NO LP FOUND, with combinations spelled out — and lpBurnPct, lpLockPct and poolLocks 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoChain 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.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

TableJSON 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, 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.
totalLiquidityUsdNoCombined USD depth across pools; pools lists them and poolCount counts them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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"
+]
  3. 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"
+}
  4. 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."
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already state readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: caching (~2 minutes), the empty-data-when-no-pool behavior and its warning interpretation, the per-chain isolation (Base pool not found under ethereum), and the semantics of the LP status verdicts including combinations spelled out. It does not contradict any annotation. It loses one point because it doesn't explicitly describe the output shape for the non-empty success case, though the output schema exists and covers that.

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 description is dense but efficient: front-loaded purpose, then verdict definitions, then usage, then caching, then edge case, then exclusions, then argument guidance. Every sentence earns its place and the structure flows from what the tool does to when to use it to edge cases. It is long, but the length is justified by the complexity of the LP status taxonomy and the per-chain caveat; a 4 because it is slightly more verbose than the minimum needed.

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 read-only analysis tool with a rich output schema, the description covers all critical operational context: LP status interpretation, empty data meaning, caching, chain matching pitfalls, and sibling routing. The annotations cover safety. The output schema exists to handle return-value details. Nothing an agent needs to invoke 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 the schema already thoroughly documents address and chain formats, examples, and enum values. The description adds meaning beyond the schema by explaining why chain matters ('pools live per chain', 'a Base pool is not found under ethereum'), warning that EVM keys require an All-Chains plan, and noting that pool/pair/wallet addresses come back as not found. This is real added value over the schema, but the schema already does most of the heavy lifting, so a 4 is appropriate rather than 5.

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 opens with a specific verb and resource ('Liquidity pool analysis for one token') and immediately states what it answers: deepest DEX, depth in USD, and LP token status. It defines the lpStatus verdicts exhaustively and explicitly distinguishes itself from price, volume, market cap, and holder tools. An agent can tell exactly what this tool is for and what it is not for.

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?

The description gives explicit when-to-use guidance ('Use it to answer whether liquidity is locked, how deep it is, and whether the position could be pulled'), names sibling alternatives for price/volume (get_token_price), market cap (get_token_scan), and holder concentration (get_holders), and adds a practical warning: a token with no pool returns empty liquidity data, which is itself a signal. It also warns about per-chain matching and that LP UNLOCKED means the position can be pulled, which directly informs agent behavior.

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

All DeFade — Multi-Chain Memecoin Analyzer toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources