Skip to main content
Glama

Pre-trade token safety (x402)

token_security_check

$0.01 via x402: pre-trade token safety / rug check for any contract — is it a honeypot, buy/sell tax, mintable, can owner reclaim ownership, transfer-pausable, blacklist, open-source, holder count, plus a DANGER/HIGH_RISK/CAUTION/OK verdict and risk flags. The call every trading and sniping agent should make BEFORE buying a token. Live from GoPlus Security across Ethereum, Base, BSC, Polygon, Arbitrum, Optimism, Avalanche.

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": {
      "address": "<address>"
    },
    "name": "token_security_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoethereum|base|bsc|polygon|arbitrum|optimism|avalanche (default ethereum)
addressYesToken contract address (0x...)
x_paymentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses cost ($0.01 via x402), data source (GoPlus Security), and the checks performed. This is transparent for a paid external API call.

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 a single paragraph with front-loaded cost and purpose. It is concise and provides necessary information without verbosity.

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?

No output schema is provided, so the description should cover return values. It mentions verdict and risk flags but does not detail the exact output structure or format. For a tool with many checks, this is a gap.

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 67% (chain and address described). The description does not add extra meaning beyond schema for these parameters. The `x_payment` parameter is not elaborated despite being part of the cost mechanism. Baseline 3 is appropriate.

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: pre-trade token safety check (rug check) with specific checks like honeypot, tax, mintable, etc. It also specifies the use case for trading and sniping agents before buying a token, and lists supported chains. This distinguishes it from sibling tools.

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 explicitly says 'the call every trading and sniping agent should make BEFORE buying a token,' clearly indicating when to use it. It does not provide when-not or alternatives, but the context is sufficient.

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