Skip to main content
Glama

Liquidity alerts

get_liquidity_alerts
Read-onlyIdempotent

Alerts from the liquidity sentinel, which reads every pool about every 1.5 seconds: pools whose base liquidity (BNB, USDT...) dropped 40% (liquidity_falling) or 70% or more (liquidity_collapsed) from their peak. Covers every pool found in the last 24 hours on PancakeSwap, Uniswap V4 and PancakeSwap Infinity. Public alerts use the latest observation; only new-pool live discovery is delayed for free access.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_liquidity_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
since_minutesNoHow far back to look

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / chain
      Removed value: -{
      -  "default": "eip155:56",
      -  "enum": [
      -    "eip155:56",
      -    "eip155:8453",
      -    "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp"
      -  ],
      -  "type": "string"
      -}
  2. Changed1 schema field changed
    • addedInput schema / properties / chain
      Added value: +{
      +  "default": "eip155:56",
      +  "enum": [
      +    "eip155:56",
      +    "eip155:8453",
      +    "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description goes further by disclosing data freshness behavior: the sentinel re-reads each pool roughly every 1.5 seconds, public alerts use the latest observation, and live new-pool discovery is delayed for free access – genuinely useful latency and staleness context an agent could not get from annotations.

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?

Three dense sentences that front-load the trigger conditions before coverage and freshness caveats. Nothing is padded, though the second and third sentences are long enough that the freshness caveat risks being skimmed past.

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

Completeness3/5

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

With no output schema, the description must convey what comes back; it names the two alert type identifiers but does not describe the returned fields, pool identifiers, or how results are ordered or paginated across the limit of 200. Adequate for understanding intent, incomplete for consuming results.

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

Parameters2/5

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

Schema description coverage is only 50% (limit has no description; since_minutes is documented as 'How far back to look'). The description never mentions either parameter, so it adds no meaning about page size, cap of 200, or how since_minutes interacts with the stated 24-hour data window.

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 concrete resource (alerts from the liquidity sentinel) and states the exact trigger conditions: 40% drawdown for liquidity_falling, 70%+ for liquidity_collapsed. It also pins the scope to pools discovered in the last 24 hours on PancakeSwap, Uniswap V4 and PancakeSwap Infinity, so the agent knows precisely what it will get back.

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

Usage Guidelines3/5

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

The data coverage and thresholds implicitly tell the agent this is a read for recent liquidity-drop events, but there is no explicit when-to-use statement, no mention of alternatives, and no exclusions. The agent must infer that it should call this rather than a generic pool/token query when hunting for depeg-style liquidity events.

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.