Crypto, web, finance and app data tools

Token Risk Check

token_risk_check

Heuristic rug and honeypot risk check of an ERC-20 before buying: owner and renouncement, upgradeable proxy, mint, pause, blacklist, fee and trading switches found in the bytecode, readable buy/sell tax, and a 0-100 risk score with flags. Ethereum, Base, Arbitrum, Optimism, Polygon.

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

Input Schema

Name	Required	Description	Default
`chain`	No		base
`token`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

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 heuristic nature, enumerates the specific checks (owner, proxy, mint, pause, blacklist, tax, switches), and states the 0-100 score output. It omits safety/read-only framing and the inherent false-positive limitation of heuristics, leaving small gaps.

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?

A single dense sentence with the core purpose front-loaded and no filler. It packs many technical checks into one line, which is efficient but slightly heavy for scanning.

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?

Given an output schema exists, the description needn't explain return values, and it covers what to call the tool with (token, chain options) and what it inspects. The heuristic's limitations and the read-only nature could be stated more explicitly, but the core is complete.

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%, so the description partially compensates by listing supported chains (Ethereum, Base, Arbitrum, Optimism, Polygon), effectively defining the chain parameter's domain. The token parameter is only implied by 'of an ERC-20', so substantial documentation is still missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb ('risk check') and resource ('ERC-20') with a specific scope ('before buying'). It does not explicitly contrast with siblings like erc20_token_info or contract_info, so sibling differentiation is implied by the risk-check framing rather than stated.

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 buying' gives a clear intended usage context, helping an agent know when to reach for it. It stops short of naming alternatives or when-not conditions, so it's solid but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?