Skip to main content
Glama

Check a Solana token

check_token
Read-only

Check a Solana token for rug-pull and scam risk. Input: a mint address, a pump fun or DexScreener link, or a $TICKER. Returns a 0-100 risk score (0-29 low risk, 30-59 caution, 60-100 high risk), plain-English red flags (mint/freeze authority, Token-2022 extensions, holder concentration, dev wallet and its launch history, linked insider wallets, LP lock, honeypot sell test, liquidity, drawdown) and a dump-model probability for tokens under 6 hours old. Read-only: never needs a wallet connection or signature. Free: 5 checks/day per IP (shared with the REST API); Pro key: unlimited. Automated risk signals, not financial advice. A low score is not a recommendation to buy.

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": {
      "query": "<query>"
    },
    "name": "check_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesMint address, pump fun / DexScreener link, or $TICKER
api_keyNoRugRadar Pro API key (optional; alternatively send Authorization: Bearer <key>).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses that no wallet connection or signature is needed, the rate-limit structure (5/day per IP shared with the REST API vs unlimited with a Pro key), that the dump model only applies under 6 hours old, and an explicit non-advice disclaimer. This is exactly the kind of auth, quota, and interpretation context annotations cannot carry.

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?

Front-loads the purpose, then inputs, then outputs, then access constraints and caveats, in a single tight paragraph. Every sentence carries distinct information — even the read-only note adds the wallet/signature detail rather than repeating the annotation verbatim.

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?

With no output schema, the description compensates by enumerating the returned risk score, its bands, the specific red-flag categories, and the conditional dump-model probability. For a two-parameter, open-world lookup tool, nothing an agent needs to call it or interpret results is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, but the description independently restates the three accepted query formats and clarifies the free-vs-Pro consequence of supplying api_key, which adds practical meaning to that optional parameter. Minor gap: it doesn't say what happens if a Pro key is supplied but invalid.

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?

Names a specific verb and resource ('Check a Solana token') and immediately scopes it to 'rug-pull and scam risk', with the accepted input types and the exact output (0-100 score with banded thresholds) spelled out. An agent can tell precisely what this returns, which distinguishes it from watch_token or scan_wallet.

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?

Usage context is clear: risk-checking a specific token via mint address, DexScreener/pump.fun link, or $TICKER, with a stated free-tier limit and Pro option. It stops short of naming when to prefer a sibling (e.g., scan_link for a link, scan_wallet for a wallet, watch_token for ongoing monitoring), so the boundary with siblings is implied rather than stated.

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.