Skip to main content
Glama

Solana Signal

Solana token rug/risk check

token_risk
Read-only

Rug/risk check for any Solana SPL or Token-2022 token mint: mint & freeze authority, dangerous Token-2022 extensions (permanent delegate, transfer hook, transfer fee), DEX liquidity, pair age, holder concentration, Jupiter verification -> 0-100 risk score, verdict (low_risk/caution/high_risk) and flags. Call this before buying an unknown token. Free tier 20/day per IP.

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

Input Schema

NameRequiredDescriptionDefault
mintYesSPL token mint address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description isn't burdened with the safety profile. It still adds real behavioral facts: the verdict enum values, that flags accompany the score, and a concrete rate limit ("Free tier 20/day per IP") that an agent must budget for. It stops short of saying whether results are cached or how fresh the liquidity/age data is, which keeps it below a 5.

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 purpose and tightly packed with no filler sentences. The arrow-chained checklist is dense but readable; it reads as one long run-on, which slightly hurts scanability for a model parsing it quickly.

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?

For a one-parameter read-only lookup with no output schema, the description covers what is inspected, what is returned (score, verdict, flags), when to call it, and the rate limit. Nothing an agent needs to invoke it correctly is missing.

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?

The single parameter has 100% schema description coverage with a base58 pattern, so the schema carries the syntax burden. The description only adds the domain framing that the mint must be an SPL or Token-2022 token mint, which is marginal but relevant; baseline 3 is appropriate.

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?

Opens with a specific verb+resource ("Rug/risk check for any Solana SPL or Token-2022 token mint") and then enumerates exactly what is inspected: mint/freeze authority, Token-2022 extensions, DEX liquidity, pair age, holder concentration, Jupiter verification. It also states the output form (0-100 score, verdict enum, flags), so the agent knows both scope and result shape without opening anything else.

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?

"Call this before buying an unknown token" gives a clear triggering condition tied to a real agent decision point. There is no explicit when-not or named alternative (e.g. token_risk_demo), but the usage context is unambiguous rather than merely 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