Skip to main content
Glama

Scan a token for rug risk

scan_token

Pre-trade token safety check (Solana and EVM): rug-pull and honeypot verdict, 0-100 safety score, mint/freeze authority, LP lock, buy/sell tax, holder concentration, deployer history and bot-volume flags.

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": {
      "mint": "<mint>"
    },
    "name": "scan_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesWallet or token address: a Solana base58 address or a 0x EVM address
chainNosolana (default), ethereum, base, bsc, arbitrum, polygon, …

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does well on output content (verdict, 0-100 score, authority flags, LP lock, taxes, holder concentration, bot-volume flags), but never states that it is a read-only lookup, whether calls cost quota or are rate-limited, or how it behaves for an unknown/unsupported token. Read-only nature is only implicit.

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?

A single tight sentence that front-loads the purpose and the chain scope before the signal list. Nothing is redundant, though the trailing signal enumeration is dense and could be trimmed or grouped.

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 no output schema, the description compensates by enumerating the returned fields, which is the most important thing an agent needs here. Remaining gaps are behavioral rather than informational: no read-only confirmation, no failure mode for unsupported chains or malformed addresses.

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%, with both `mint` (Solana base58 or 0x EVM address) and `chain` (default solana, list of values) fully documented in the schema. The description adds only the high-level 'Solana and EVM' framing and no per-parameter guidance, so it sits at the baseline for a fully documented schema.

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?

States a concrete verb+resource combination ('Pre-trade token safety check') with explicit chain scope (Solana and EVM) and enumerates the signals returned, so an agent knows exactly what the tool produces. It does not name or differentiate against the siblings deployer_reputation and check_agent_wallet, which overlap on 'deployer history' and wallet 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 phrase 'Pre-trade token safety check' implies the usage context (vetting a token before buying), but there is no explicit when-to-use/when-not, no statement about how it differs from deployer_reputation, and no mention of prerequisites such as a known mint address. Usage is inferable but not guided.

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.