Skip to main content
Glama

Base Token Safety Inspector

token_deep_safety_check

Deep Base token safety / rug-pull / honeypot check: everything in token_safety_check plus DEX liquidity (Uniswap, Aerodrome), holder shares, mint/blacklist/fee functions, a simulated buy, and a 0-100 risk score with a low/medium/high verdict. Price: $0.02 USDC on Base via x402.

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_deep_safety_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 payment cost ($0.02 USDC on Base via x402), the chain scope (Base), and the nature of the 'simulated buy' (simulation, not a real transaction). It omits latency, rate limits, and behavior when a token is not found or not on Base.

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

Conciseness5/5

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

One dense, front-loaded sentence listing scope and outputs, followed by the price disclosure. No filler; every clause adds information.

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?

For a single-parameter tool with no annotations and no output schema, the description names the returned artifacts (risk score and verdict, plus the individual checks) and the cost, which covers most of what an agent needs. Missing only failure modes and pagination/latency details, which are minor here.

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 0% and the single 'address' parameter has no description, so the definition must compensate. 'Deep Base token safety check' implies the address is a Base token contract, but it never states that explicitly nor clarifies contract-vs-pool address or accepted format.

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?

States a specific check ('Deep Base token safety / rug-pull / honeypot') and enumerates exactly what the deep variant covers: DEX liquidity on Uniswap/Aerodrome, holder shares, mint/blacklist/fee functions, a simulated buy, and a 0-100 risk score. The phrase 'everything in token_safety_check plus...' explicitly distinguishes it from the sibling tool.

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 'everything in token_safety_check plus X' framing gives a clear basis for choosing this tool over the sibling when deeper due diligence is needed. It stops short of an explicit when-to-use/when-not-to-use rule or naming a cheaper alternative for quick checks, but the comparative context is clear.

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