Skip to main content
Glama
yg-base-mcp
by ufo1898

tokenrisk

Check Base token risk by address: honeypot status, buy/sell taxes, safe exit size, pool age, and holder concentration, paid per call in USDC.

Instructions

任意 Base 代币风险体检:蜜罐判定、买卖税、可安全退出规模、池龄与持币集中度(?address=0x…) — 0.005 USDC per call (x402, Base USDC, no signup)

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

Input Schema

NameRequiredDescriptionDefault
addressYesBase address 0x…
_paymentNobase64 PAYMENT-SIGNATURE from a previous 402 challenge

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add genuine value by disclosing the commercial model: 0.005 USDC per call over x402 on Base, no signup required, which explains the _payment parameter and the 402 challenge flow. What it omits is equally material — it never says the checks are read-only simulations, how latency or re-billing works, or what happens when a token is unverified or the payment header is rejected.

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?

A single front-loaded sentence that leads with the capability and its outputs, then appends pricing as a trailing clause. Every element earns its place and there is no filler.

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?

There is no output schema, so the enumerated check dimensions are the agent's only guide to the return shape, and they cover the essential fields reasonably well. Still missing for a paid, payment-gated tool: what the response looks like for the risky/unknown cases, error behavior for non-Base addresses or expired payment signatures, and whether a failed honeypot check still costs 0.005 USDC.

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 both parameters are already documented in the schema. The description's '(?address=0x…)' merely echoes the address parameter format without adding syntax or constraints, and it says nothing about _payment beyond the pricing line. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('risk checkup for any Base token') and enumerates exactly what is measured: honeypot verdict, buy/sell tax, safe exit size, pool age and holder concentration. This makes it unmistakably distinct from the contextual siblings (pools, yields, wallet, arb), which cover pool analytics, yield, wallet and arbitrage rather than token-level contract risk.

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?

The '任意 Base 代币' (any Base token) phrasing is a scope statement and implicitly tells the agent to use this before trading or assessing an unknown token. However, there is no explicit when-not guidance, no mention of on-chain versus unverified contracts, and no named alternative such as free_sample or pools when the agent only needs liquidity data.

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