Skip to main content
Glama

audit_crypto_token

Audit any Base, Ethereum, Arbitrum, Optimism, Polygon, BSC, Avalanche, or Solana token contract for honeypots, buy/sell taxes, hidden ownership, whale concentration, LP locks, live DEX liquidity depth, and AMM slippage impact for an intended USD order size. On Base, Ethereum, BSC, Arbitrum, Optimism and Polygon, when the token has a V2-style pool against the chain's wrapped native coin, it also simulates a real buy -> sell round trip to measure actual taxes and check that the token can be sold ($0.01 USDC on Base).

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": {
      "tokenAddress": "<tokenAddress>"
    },
    "name": "audit_crypto_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoTarget chain (defaults to 'base' for 0x addresses or 'solana' for Base58)
tokenAddressYes0x-prefixed EVM token contract address or Base58 Solana mint address
intendedOrderUsdNoIntended swap size in USD to estimate AMM pool price impact (default 1000)
paymentSignatureNoOptional x402 v2 base64 PAYMENT-SIGNATURE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 burden and does well: it discloses the supported chain set, the conditional simulation behavior (only V2-style pools against the wrapped native coin, and only on six named chains), and a concrete cost of $0.01 USDC on Base. It stops short of covering failure modes, rate limits, or whether payment is mandatory given paymentSignature is optional, which prevents 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?

Two sentences, with the core capability and the risk checklist front-loaded ahead of the conditional simulation on Base/Ethereum/BSC and peers. Dense but essentially waste-free; the second sentence is long and packs several conditions, mildly testing readability.

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?

No output schema exists, so the description must convey what comes back, and the enumerated checks serve that role reasonably well. Given a multi-chain tool with a paid simulation step, it is nearly complete; it omits output shape, result interpretation, and error behavior for unsupported chains or non-V2 pools.

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 the baseline is 3. The description does add some meaning by framing intendedOrderUsd as the swap size used to estimate AMM pool price impact, and its chain list matches the chain enum, but it adds nothing about the tokenAddress format or the paymentSignature parameter beyond schema text.

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 names a specific verb (audit) and resource (token contract) and enumerates the exact risk dimensions checked: honeypots, buy/sell taxes, hidden ownership, whale concentration, LP locks, liquidity depth, and slippage impact. This is enough to distinguish it from chain_token_info (lookup) and token_verdict (verdict) without opening any schema.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'Audit any ... token contract' and the due-diligence checks listed, so it is clear when the tool is relevant. However, the description never states when NOT to use it or routes the agent to sibling tools like token_verdict or chain_token_info, leaving selection to inference.

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.