Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

tool_token_honeypot

[x402 paid: $0.002 USDC on Base] Honeypot/scam risk check for a Base token: liquidity + LP heuristics scored 0-100, LLM explains the flags. Honest method: heuristics, not tx simulation. tools/call returns the live payment challenge.

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

Input Schema

NameRequiredDescriptionDefault
addressNoexample: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the price ($0.002 USDC on Base), that a tools/call returns a live payment challenge before results, and honestly limits the method to heuristics rather than tx simulation, which sets expectations about false negatives. It does not state rate limits, failure modes for invalid/non-Base addresses, or whether payment is charged on failure, so it stops short of full behavioral disclosure.

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?

Three compact sentences, front-loaded with the payment tag and then the core purpose, followed by method caveat and payment mechanics — no filler. The bracketed pricing prefix is dense but scannable; nothing here is redundant.

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 no output schema, the description correctly conveys the return shape (0-100 score plus an LLM explanation of flags) and the x402 payment handshake, which is the non-obvious part of invoking it. The main remaining gap is clarifying the address parameter (contract vs wallet) and behavior on invalid input, but overall it is complete enough to call correctly.

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 the schema already documents the single parameter, and the baseline of 3 applies. However, the description adds no meaning beyond the schema — it never says the address is the token contract address (as opposed to a wallet or pair), nor why the sole parameter is not marked required, which is a genuine ambiguity an agent would face.

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 states a specific verb and resource: a honeypot/scam risk check for a Base token, with the inputs it scores (liquidity + LP heuristics, 0-100) and what it returns (LLM explanation of flags). It distinguishes the method from simulation-based tools ('heuristics, not tx simulation'), but it does not name or contrast any sibling (e.g. token-safety-pack or token_token_verdict), leaving the choice between similar-sounding tools to inference.

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?

Scope is implied by 'for a Base token' and the method caveat suggests when this is preferable to tx-simulation checks, but there is no explicit when-to-use / when-not-to-use statement or named alternative. Cost and payment-flow information is present, which helps an agent decide whether to call, but the routing guidance itself is only implied.

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.

Resources