Skip to main content
Glama

Rug alert

rug_alert

X1 rug alert feed ($0.002): tokens on X1 whose mint or freeze authority remains live. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
hoursNolookback window in hours, e.g. 24
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses that this is a paid operation, the exact cost ($0.002/call), the payment rail (x402, USDC on Arc/Base/Solana or XNT on X1), and the required two-step handshake. It does not describe the returned record shape or how a failed/unpaid call behaves, which keeps it from a 5.

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 sentences, front-loaded with what the feed is and what it costs before the mechanics, so the agent gets the essentials first. The price is stated twice ($0.002 in the opening clause and again in the payment sentence), a small redundancy.

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?

For a 2-parameter paid feed with no output schema, the description covers purpose, cost, currency options, and the payment workflow an agent must follow. The remaining gap is what a returned token entry contains and whether `hours` has a default, neither of which is stated.

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 both parameters are already documented, establishing a baseline of 3. The description reinforces the `payment` semantics (pass the signed payload to complete the purchase in-call) but says nothing about `hours` beyond what the schema's example already conveys.

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?

"X1 rug alert feed ... tokens on X1 whose mint or freeze authority remains live" gives a concrete verb-equivalent (feed/list) and a precise selection criterion, so an agent knows exactly what data this returns. It does not name any sibling (e.g. wallet_alert) to contrast against, which keeps it short of a 5.

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?

The description gives explicit procedural guidance for invocation: call once without `payment` to obtain terms, sign with your own wallet, then call again with `payment`. It does not say when to prefer this feed over related alert tools, so context is clear but alternatives are absent.

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