Skip to main content
Glama

rug_monitor

Read-onlyIdempotent

Get alerted the moment liquidity is pulled — Pay once to watch a Base token's liquidity. We snapshot a baseline and, every 30 minutes, POST your webhook if liquidity collapses (a liquidity pull — the actual moment of a rug). Not price moving — the pool being drained out from under you. Deliveries are HMAC-signed (secret returned once at registration) and retried up to 3 times. Expires after 30 days. Required input: token. Priced $0.10 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls (no free tier on this tool). No API key required.

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": {
      "token": "<token>"
    },
    "name": "rug_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkNoOr: monitor id to poll its status
tokenYesToken address
dropPctNoFire on liquidity drop % (default 50)
webhookNoWebhook URL (optional — omit to poll)

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / data / description
      Previous value: -"The result payload. Shape is service-specific; every field is documented in the service description above."New value: +"The result payload. Shape is service-specific; every field is documented in the tool description."
  2. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "data"
      -]
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations: 30-minute polling cadence, HMAC-signed deliveries with the secret returned once, up to 3 retries, 30-day expiry, $0.10 per call over x402 on Base, and no free tier. Minor tension with readOnlyHint=true since registration creates persistent state and yields a one-time secret, but the description does not actually claim chain mutation, so it is not a contradiction.

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 value proposition and alerting mechanism are front-loaded and every sentence carries information about delivery, pricing, or lifetime. There is mild redundancy in the double framing of a liquidity pull ("the actual moment of a rug" / "the pool being drained out from under you").

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

Completeness4/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 need no explanation, and the description covers the operationally important unknowns: cost model, payment header, authentication of deliveries, retry and expiry behavior. The only gap is the polling path via check and the dropPct threshold, both left entirely to the schema.

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

Parameters3/5

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

Schema coverage is 100%, so all four parameters are already documented, and the description mostly repeats that ("Required input: token") or restates the webhook-omission behavior already in the schema. It never mentions check or dropPct, so it adds no new meaning over the structured definitions; baseline 3 applies.

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

Purpose4/5

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

"Get alerted the moment liquidity is pulled" plus "watch a Base token's liquidity" gives a concrete verb-and-resource, and the contrast "Not price moving — the pool being drained" sharpens what is being monitored. It does not name a sibling (e.g. rug_score) to distinguish alerting from scoring, so the boundary is stated only implicitly.

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

Usage Guidelines4/5

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

Clear conditions for use: watch a token's liquidity rather than price, supply a webhook to be pushed, or "omit to poll"/use check to poll status instead. No explicit exclusion against sibling tools such as rug_score, but the usage context is unambiguous enough to act on.

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