Skip to main content
Glama
dbe006

rugguard-mcp

by dbe006

pretrade_check

Evaluate token risk before trading: get a prescriptive block, caution, or allow decision and a clamped max exposure based on your risk policy and trade size.

Instructions

Pre-trade firewall: returns a prescriptive block | caution | allow decision plus a clamped max_suggested_exposure_usd, given a token, a trade size, and the agent's risk policy.

Costs $0.01 USDC on Base via x402 (same price as scan_token). Returns a signed JSON report when the deployment has signing configured — the signature and key_fingerprint fields prove what RugGuard said at the moment of trade, verifiable offline via the rugguard-verify CLI (pip install rugguard-verify) or against GET /v1/pubkey.

Args: chain: base or solana. address: Token contract address (EVM 0x… or Solana base58). intended_trade_usd: Trade size in USD. Used to clamp the returned max_suggested_exposure_usd. Must be > 0 and ≤ $1B. policy: Agent risk tolerance. One of: - conservative — block at medium_risk or worse (score ≥ 51) - balanced — block at high_risk or worse (score ≥ 71) [default] - aggressive — block at critical only (score ≥ 91) An uncertain verdict (sparse data) returns caution in all modes — absence of evidence is not evidence of safety.

Returns: On success: { scan_id, chain, contract, policy_recommendation: block | caution | allow, policy, risk_score: 0-100, verdict, confidence, reason: [{code, severity}, ...], # top 3 flags max_suggested_exposure_usd: float, # 100% if allow, 20% if caution, 0 if block intended_trade_usd, scanned_at, disclaimer, signature, key_fingerprint # null when signing is unconfigured } On failure: {error, message}. Same error codes as scan_token.

Disclaimer integrity: the disclaimer field is inside the signed bytes. Stripping or rewriting it breaks signature verification by design — a downstream proxy that drops the disclaimer will cause rugguard-verify to reject the report. That is the point.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYes
policyNobalanced
addressYes
intended_trade_usdYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description discloses cost ($0.01 USDC), signing/verification, disclaimer integrity, and decision logic per policy. No annotations are provided, so the description carries full burden and does so thoroughly.

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-structured and front-loaded with the key output. While comprehensive, it is slightly lengthy but every sentence adds value.

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 and that an output schema exists, the description is complete, covering return values, edge cases (uncertain verdict), and disclaimer integrity. It complements the schema well.

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?

Schema coverage is 0%, but the description fully explains each parameter: chain (base/solana), address format, intended_trade_usd constraints, and policy options with defaults. This adds significant meaning beyond the schema.

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 function as a pre-trade firewall returning a decision (block/caution/allow) and clamped exposure. It distinguishes itself from siblings (scan_token, explain_scan) by its specific pre-trade role.

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 explains when to use the tool (pre-trade check) and details the policy parameter's behavior. It implies usage context but does not explicitly state when not to use or compare with siblings.

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