Skip to main content
Glama

ZK Provenance, RFC 9421 Web Bot Auth & Counterparty KYB MCP

Audit Honeypot/Tax & Assemble 0.35% Non-Custodial Token Snipe Calldata

safe_snipe_swap_with_honeypot_firewall
Read-onlyIdempotent

Runs GoPlus + DexScreener honeypot/tax firewall first and, only if safe, builds ready-to-sign 0.35% non-custodial multi-DEX swap calldata (saving 65% vs 1% Telegram sniper bots).

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

Input Schema

NameRequiredDescriptionDefault
senderNoOptional trader 0x wallet address
chainIdNoEVM chain ID ('8453' Base, '42161' Arbitrum, '1' Ethereum, '137' Polygon, '10' Optimism)
amountUsdcNoUSDC input amount (default 100)
tokenAddressNoTarget 0x token contract address or symbol to buy with USDC
maxSpendCapUsdNoMax per-trade spend cap in USD (default 250)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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, destructiveHint=false, openWorldHint), and the description adds real context: it calls two third-party APIs, gates all downstream work on the audit result, and returns 'ready-to-sign' calldata rather than executing anything, which is consistent with the read-only hint. It does not disclose the failure mode when the firewall rejects a token (error vs. structured report), leaving one behavioral gap.

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?

It is a single front-loaded sentence with the firewall-first condition stated before the calldata-assembly outcome, which is the right ordering for an agent scanning for prerequisites. The trailing parenthetical about saving 65% versus Telegram sniper bots is unverifiable marketing that does not help invocation, keeping it from a 5.

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 five all-optional parameters and no output schema, the definition is adequate on inputs but silent on what the response actually contains, whether that is calldata plus an audit verdict or a rejection reason. For a tool whose main value is producing structured swap payloads, that missing return description is a material gap.

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%, so every parameter including the USDC default of 100, the spend cap of 250, the chain-ID enumeration and the token symbol-or-address option is already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

The description names two concrete operations: a GoPlus + DexScreener honeypot/tax audit and the assembly of multi-DEX swap calldata, so an agent knows exactly what the tool produces. It is distinguishable from siblings like audit_token_contract_technical_risks or plan_and_build_guarded_rebalance_swap by the combined audit-then-build flow, though it never names those siblings to make the contrast explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: the tool is for sniping a token with USDC after a safety check, and the 'only if safe' clause describes internal sequencing rather than when an agent should pick this tool. There is no explicit when-not guidance or pointer to the audit-only or rebalance siblings, so an agent must infer routing from the names.

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.