Skip to main content
Glama

Token security check (x402)

token_security_check

Read-onlyIdempotent

$0.01 via x402: pre-trade token safety / rug check for any contract — is it a honeypot, buy/sell tax, mintable, can owner reclaim ownership, transfer-pausable, blacklist, open-source, holder count, plus a DANGER/HIGH_RISK/CAUTION/OK verdict and risk flags. The call every trading and sniping agent should make BEFORE buying a token. Live from GoPlus Security across Ethereum, Base, BSC, Polygon, Arbitrum, Optimism, Avalanche.

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

Input Schema

NameRequiredDescriptionDefault
chainNoethereum|base|bsc|polygon|arbitrum|optimism|avalanche (default ethereum)
addressYesToken contract address (0x...)
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), and the description adds genuinely new context: the $0.01 x402 price, the 'Live from GoPlus Security' upstream source, and the concrete verdict labels DANGER/HIGH_RISK/CAUTION/OK with risk flags. It does not discuss rate limits, latency, or failure behavior when a chain or contract is unsupported, which keeps it out of 5 territory.

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?

The price and payment model are front-loaded, then the capability list, then the call-to-action, which is a sensible order for an agent scanning the definition. The middle checklist is long and runs as one em-dash clause, but every item is a distinct, decision-relevant check rather than filler.

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 correctly carries the burden of describing returns via the check list, verdict tiers, and risk flags, and it discloses cost and the payment-terms-first flow. It omits what happens for an unsupported chain or an invalid contract address, and gives no sense of response latency or payload size, so it is complete but not exhaustive.

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 100%, with the chain enum listed, the address format (0x...) specified, and the x_payment handshake explained in the schema itself. The description adds no syntax or format detail beyond that; its enumerated checks describe outputs rather than parameter meaning. Baseline 3 is appropriate when the schema carries the load.

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 verb-and-resource pair ('pre-trade token safety / rug check for any contract') and backs it with an enumerated checklist (honeypot, buy/sell tax, mintable, ownership reclaim, pausable transfers, blacklist, open-source, holder count) plus the verdict taxonomy. That enumeration distinguishes it from generic address-risk siblings like get_crypto_address_risk and from aggregators like pretrade_full_report without opening a 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 explicit timing guidance: 'The call every trading and sniping agent should make BEFORE buying a token,' which tells the agent exactly when this belongs in a workflow. It stops short of naming an alternative or a when-not-to-use condition (e.g., how it relates to pretrade_full_report or chain_token_identity), so it lands at 4 rather than 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.

Resources