Skip to main content
Glama

Agent safety checks: prompt-injection scan, honeypot check, x402 preflight + crypto data (USDC/x402)

Honeypot and rug-pull check for an ERC-20 before swap or approve

token_risk
Read-only

Honeypot and rug-pull check for an ERC-20 on Base or Ethereum before a swap, approval or signature, read straight from the contract: upgradeable proxy (EIP-1967, beacon, clone), owner powers in the bytecode (mint, pause, blacklist, fee or max-tx setters, trading switch, burn from any address), owner renounced or active and the owner's share of supply; known issuers labeled. Risk low, medium or high with reasons. Signals, not investment advice. 0.015 USDC base (new payers 0.015, >10 payments 0.0105; 1 pack call). After: gas-window before you trade on that chain (the result's next field has the exact call).

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": {
      "token": "<token>"
    },
    "name": "token_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNo
tokenYes
payment_txNoHash of a USDC transfer on Base to payTo (≥ the price, ≤ 72 h old) instead of an x402 signature.
bundle_tokenNoToken from buy_signal_pack, buy_subscription (pro/desk) or buy_enterprise instead of paying per call.
payer_addressNoWallet you pay from: the payment-required error quotes your tier (0 payments base price (new-payer surcharge paused), 1-10 base, >10 -30 %) and, from the third payment, an upgrade with your own spend.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses the analysis surface, the output shape (low/medium/high risk with reasons), a scope disclaimer ('signals, not investment advice'), and a full pricing model with tier discounts and pack-call accounting. The payment paths (payment_tx, bundle_token, payer_address tier quoting) are explained in behavioral terms the annotations cannot express.

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?

Purpose is front-loaded in the first clause, and the trailing 'After:' routing hint earns its place. The middle is a dense parenthetical enumeration and the pricing sentence is crammed with semicolons, which costs some readability but not much length.

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?

With no output schema, the description still conveys the return shape (risk tier plus reasons, plus a `next` field) and covers the payment flow end to end. It is silent on failure modes such as unsupported or non-contract tokens, which is the main remaining gap for a five-parameter read 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 coverage is 60% and the schema already documents payment_tx, bundle_token, and payer_address in detail, so the description mostly reinforces rather than extends it. It does add the concrete price (0.015 USDC base, 0.0105 above 10 payments) that the schema only alludes to as 'base price', but it says nothing about the required `token` parameter beyond the address being read from the contract.

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 states a specific check (honeypot/rug-pull) on a specific resource (ERC-20 on Base or Ethereum) and enumerates exactly what is inspected: proxy patterns (EIP-1967, beacon, clone), owner powers in bytecode (mint, pause, blacklist, fee setters, trading switch), renouncement status, and owner supply share. An agent can distinguish this from get_swap_route or buy_pack_with_card 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 Guidelines4/5

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

It gives a clear trigger — run it 'before a swap, approval or signature' — and adds a follow-on step ('After: gas-window before you trade on that chain'). It does not name an alternative tool or state when not to use it, so it stops short of full routing guidance.

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