Skip to main content
Glama
dbe006

rugguard-mcp

by dbe006

scan_token

Scan a token contract for rug-pull risk before trading. Get a structured report with risk score, verdict, and flags.

Instructions

Run a pre-trade rug-pull risk scan on a token contract.

Returns a structured risk report. Pays $0.01 USDC on Base behind the scenes via x402. The spend is tracked against per-session and 24 h caps configured in the MCP server — if a cap is breached the call returns a spend_cap_exceeded error WITHOUT signing.

Args: chain: Chain identifier. base for Base mainnet EVM token (14 heuristics). solana for Solana SPL mint (5 heuristics). address: Token contract address — 0x... for EVM, base58 mint address for Solana.

Returns: On success: {score: 0-100, verdict: safe|low_risk|medium_risk|high_risk|critical|uncertain, score_confidence: high|medium|low|insufficient_data, rug_probability_30d: 0.0-1.0, flags: [{code, severity, evidence}, ...], scan_id: uuid for follow-up via explain_scan(...)}. On failure: {error, message}. error is one of missing_credentials, spend_cap_exceeded, payment_failed, request_failed, non_200.

In demo mode (RUGGUARD_MCP_DEMO=1 or `--demo`): returns one of three
canned scenarios deterministically by `address[-1]`. Response has
`_demo: true` — never trade on this. No wallet, no network call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYes
addressYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description fully discloses behavior: payment of $0.01 USDC on Base via x402, per-session and 24h spending caps leading to a spend_cap_exceeded error, demo mode with canned responses, and detailed error types. This covers all critical behavioral aspects.

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 well-organized with 'Args' and 'Returns' sections, front-loading the purpose. It is thorough but not overly verbose; every sentence adds value. A slight trim could be made, but it remains highly effective.

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?

Given the tool's complexity (payment, caps, demo, multiple chains) and the presence of an output schema, the description covers all necessary aspects: return structure on success and failure, error types, demo behavior, and parameter constraints. It is fully complete.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description adds essential meaning. It specifies the allowed values for chain ('base' for EVM, 'solana' for SPL mint) and the address format ('0x...' for EVM, base58 for Solana). This goes well beyond the schema's bare property titles.

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 clearly states the tool's purpose: 'Run a pre-trade rug-pull risk scan on a token contract.' It specifies the verb (scan), the resource (token contract), and the output (structured risk report). The mention of returning a risk report distinguishes it from siblings like explain_scan and pretrade_check.

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 provides context for when to use the tool (pre-trade risk scan), details about payment and spending caps, and error conditions. It does not explicitly exclude usage scenarios or name direct alternatives, but the purpose is clear enough for correct selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dbe006/rugguard-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server