Skip to main content
Glama
Sign In
x402-btc-radar

x402-btc-radar

by gaodongmei478
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Token risk / honeypot check ($0.01)

token_risk
Read-only

Runs a pre-trade safety check on a Base or BSC token, simulating honeypot buys/sells and reporting taxes, risky flags, holder concentration, liquidity, pool age, verdict, and score.

Instructions

PAID $0.01 USDC on Base via x402 (paid from the caller's own wallet). Pre-trade safety check for one Base or BSC token: honeypot buy/sell simulation, buy/sell tax, mint/pause/blacklist/proxy/owner flags, holder concentration, liquidity, pool age. Returns verdict low|medium|high|honeypot, 0-100 score, action and reasons. Invalid input returns 400 and is not charged. Not investment advice.

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

Input Schema

NameRequiredDescriptionDefault
chainYesbase (8453) or bsc (56)
addressYestoken contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation: discloses the $0.01 USDC x402 payment drawn from the caller's wallet, enumerates the checks performed, names the possible verdicts and score range, and states that invalid input returns 400 uncharged. That payment and failure-mode disclosure is exactly what an agent needs before invoking a paid tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded: cost and payment mechanism first, then scope, then what is checked, then output shape and error behavior. No filler, and the disclaimer closes it in five words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description still specifies return fields (verdict enum, 0-100 score, action, reasons). Combined with the payment and error semantics, nothing material is left for the agent to guess.

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% and both params (chain enum, address pattern) are already documented in the schema. The description adds only the implicit 'single token per call' constraint, so this is baseline-level added meaning.

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?

"Pre-trade safety check for one Base or BSC token" names the verb, resource, and scope precisely, and lists the concrete checks (honeypot simulation, taxes, mint/pause/blacklist flags, holders, liquidity, pool age). The word "one" implicitly separates it from the sibling token_risk_batch.

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?

"Pre-trade safety check" gives a clear trigger condition, and the 400/not-charged clause tells the agent bad input is free. It stops short of explicit when-not guidance (e.g. use batch for multiple tokens, or skip for non-Base/BSC chains).

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

Deploy Server

Other Tools