Skip to main content
Glama

EIP-7702 Smart-Wallet, Passkey Session Key & Gas-Optimizer MCP

Audit ERC-20 Token Bytecode for Honeypot, Tax & Liquidity Risks

audit_token_contract_technical_risks
Read-onlyIdempotent

Checks GoPlus and DexScreener telemetry for honeypot traps, buy/sell tax %, hidden owner privileges, and live pool liquidity before swapping.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_token_contract_technical_risks"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdNoEVM chain ID (default '8453')
tokenAddressNo0x ERC-20 contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description usefully adds that results come from third-party GoPlus and DexScreener telemetry, which implies an external network dependency and third-party data reliability, but it says nothing about failure modes, unsupported chains, or what a verdict looks like.

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?

A single sentence that front-loads the data sources and then enumerates the risks checked, with zero filler wording. Every clause carries information an agent needs.

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?

With two simple parameters and read-only annotations, the input side is adequately covered. However, there is no output schema, and the description never indicates what is returned (a score, a boolean verdict, a structured risk report) or how to interpret it, which is a meaningful gap for an audit tool.

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%, with both chainId (default '8453') and tokenAddress already documented in the schema, so the baseline of 3 applies. The description adds no meaning about address normalization, chain support, or the fact that tokenAddress is effectively required despite no required parameters being declared.

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 verb (checks telemetry) plus the exact risk categories it evaluates: honeypot traps, buy/sell tax %, hidden owner privileges, and pool liquidity. This clearly separates it from the sibling build/plan/simulate tools, which construct or execute transactions rather than assess token risk.

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 phrase "before swapping" gives an explicit decision point for when to call it, which is a real usage guideline rather than a vague implication. It stops short of naming alternatives or stating what to do when the token is not covered, so it falls short of a 5.

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.