Skip to main content
Glama

audit_token

Scans live EVM bytecode, Solana mint accounts, and DexScreener liquidity to detect rug pulls, honeypots, hidden blacklists, and mint/freeze authority risks before you buy a token.

Instructions

Live on-chain token & smart contract rug/honeypot shield for Base, Ethereum, and Solana. Inspects live EVM bytecode (hidden blacklists, mutable 99% tax fees, pause switches, unverified proxies), Solana SPL / Token-2022 mint accounts (active Mint Authority, Freeze Authority, Permanent Delegate wallet seizure, Transfer Hooks), and live DexScreener liquidity & buy/sell honeypot telemetry. Cost: $0.05 USDC or 0.00035 SOL.

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": {
      "chain": "<chain>",
      "token_address": "<token_address>"
    },
    "name": "audit_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesTarget blockchain networkbase
payment_txNoSolana signature or Base 0x transaction hash for x402 payment (0.00035 SOL or 0.05 Base USDC)
session_tokenNoPrepaid ScanPay session voucher token (sp_sess_...)
token_addressYesToken contract address (0x...) or Solana Mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose valuable behavior: it reads live bytecode and live market telemetry rather than cached data, and it states pricing ($0.05 USDC / 0.00035 SOL), which explains the payment parameters. However, it never explicitly states the operation is read-only and non-mutating, gives no rate limits or latency expectations, and says nothing about the response shape despite there being no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the cost sentence earns its place, but the body is one long comma-spliced feature dump ('hidden blacklists, mutable 99% tax fees, pause switches, unverified proxies...') that reads as sales copy. The detail is behaviorally useful, yet it could be tightened and split into scannable clauses without losing meaning.

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?

For a 4-parameter, no-annotation, no-output-schema tool, the definition explains what is inspected and what it costs, which is the core an agent needs. It still leaves gaps on the return value (is it a verdict, a risk score, a list of findings?), how payment_tx and session_token interact or which takes precedence, and failure behavior for unsupported chains or invalid addresses.

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 description coverage is 100%, so all four parameters (chain enum, token_address, payment_tx, session_token) are already documented in the schema and the baseline is 3. The description adds only indirect context, namely the cost figures that motivate payment_tx versus session_token, and does not explain address formats or payment-flow ordering beyond what the schema states.

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?

The description names a concrete resource ('live on-chain token & smart contract') and concrete inspection targets (EVM bytecode, Solana SPL/Token-2022 mint accounts, DexScreener liquidity telemetry) across three named chains. It is clearly not scrape_url or simulate_tx, though the headline phrase 'rug/honeypot shield' is more marketing than verb. Purpose is unmistakable, with a slight deduction for the promotional framing over a clean verb+resource statement.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, no reference to any sibling tool, and no stated prerequisites beyond cost. An agent can infer this is for pre-trade token due diligence, but nothing in the text instructs it to prefer audit_token over simulate_tx or scan_code, or clarifies which chains/contracts are out of scope.

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