Skip to main content
Glama

Grok Crypto Quant API

Token scam / honeypot risk check

token_check
Read-onlyIdempotent

Token scam check in one call instead of wiring up five data sources: honeypot sell simulation, unverified code, mint/pause/blacklist powers, taxes, upgradeable proxy, age, liquidity, fake major-token (e.g. fake USDC) lookalikes and spam-airdrop patterns. Base, Ethereum or Solana. Never visits metadata URLs. Price: $0.02 USDC per call (x402, Base mainnet). Free pre-check: validate_token_check.

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_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesbase, ethereum or solana
addressYesToken contract / mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial context that annotations cannot convey: a per-call price of $0.02 USDC via x402 on Base mainnet, and the explicit promise that it never visits metadata URLs (a real exfiltration/timing concern). The readOnly/idempotent/openWorld hints align with the 'check, not mutate' framing, so nothing is contradicted.

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 core value proposition and packed into essentially two dense sentences with no filler. The long signal enumeration is on the edge of a run-on list but each item carries decision-relevant information, so it mostly earns its space.

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?

With only two required parameters, annotations covering the safety profile, and a sibling designated for the free pre-check, the description covers what an agent needs to decide and invoke. The one gap is the shape of the verdict itself — with no output schema, the description could say what the risk result looks like beyond the signal list.

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 only restates the chain set ('Base, Ethereum or Solana'), duplicating the enum, and adds nothing about the address format or chain-specific address differences. Baseline 3 applies.

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 concrete verb+resource (token scam/honeypot risk check) and enumerates the specific signals it evaluates — honeypot sell simulation, mint/blacklist powers, taxes, proxy upgradeability, liquidity, lookalikes. The scope statement 'Base, Ethereum or Solana' and the contrast with 'wiring up five data sources' makes it unmistakable against siblings like backtest or market_signals.

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?

Tells the agent when to reach for it (consolidated multi-source risk assessment) and explicitly routes to the cheaper alternative with 'Free pre-check: validate_token_check.' It does not spell out when NOT to use this paid call versus the free validator, leaving the escalation condition implicit.

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