Automaton Onchain Tools

base_honeypot_check

Use when: can I sell this Base token, and what is the buy/sell tax? Can you actually sell this Base token? Simulates a small buy and a sell back into its deepest WETH pool (Uniswap V2/V3 and Aerodrome) with an eth_call, so nothing trades. Returns sellable yes/no, buy tax %, sell tax %, the pool used, a verdict (sellable, taxed, high tax, honeypot) and coverage notes. No pool, not a token or an inconclusive simulation is not charged. Costs $0.01.

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": "base_honeypot_check"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.1/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 eth_call simulation mechanism, that nothing actually trades, what is returned (sellable, taxes, pool, verdict), and billing semantics including which inconclusive cases are not charged. Missing only auth/rate-limit context, which is minor here.

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?

Front-loaded with the use case, then mechanism, returns, and pricing in a logical order. Slightly dense as a single run-on block, but nearly every clause (including the no-charge conditions) earns its place.

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 one-parameter simulated-call tool with no output schema, the description covers mechanism, output fields, verdict taxonomy, and cost/no-charge rules. An agent has enough to call it and interpret the result.

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?

Only one parameter (token) at 0% schema description coverage; the description implies a Base token address but adds no format or validation detail beyond the schema's regex pattern. Minimum viable given the single-parameter surface.

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 and resource: simulates a small buy and sell back into the deepest WETH pool to determine sellability and buy/sell tax for a Base token. Chain scope ('Base') distinguishes it from bsc_honeypot_check and ethereum_honeypot_check siblings.

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?

Opens with an explicit 'Use when:' trigger phrased as the user question it answers ('can I sell this Base token'). No explicit when-not or exclusion clause, but the chain-specific naming implicitly routes non-Base cases to siblings.

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

All Automaton Onchain 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?