Skip to main content
Glama

Token Risk Solana

token_risk_solana
Read-onlyIdempotent

Rug-pull / scam RISK SCREENING for a Solana SPL token. Pass the token MINT address. Detects active mint authority (supply can be inflated), freeze authority (your balance can be frozen), closable/mutable-metadata flags, transfer fees/hooks, and holder + LP concentration. Returns a computed red_flags[] list plus the raw GoPlus Security facts. Keyless, live on-chain. Use for "is this Solana token safe / a rug?".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contract_address": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"
    },
    "name": "token_risk_solana"
  }
}

Input Schema

NameRequiredDescriptionDefault
contract_addressYesThe SPL token mint address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "contract_address": "EPjFWaLb3odccxiLVXACsimbMbGgRs3YzNqEHFx5THv"
      -  },
      -  {
      -    "contract_address": "So11111111111111111111111111111111111111112"
      -  }
      -]New value: +[
      +  {
      +    "contract_address": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"
      +  },
      +  {
      +    "contract_address": "So11111111111111111111111111111111111111112"
      +  }
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds real context on top: keyless access, live on-chain data, the GoPlus Security source, and the shape of the result (red_flags[] plus raw facts). It does not cover latency, rate limits, or behavior for invalid/non-SPL addresses, which keeps it off 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the verb and resource, then the detection list, then the return shape and use case. Every clause carries information and nothing is padded.

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?

For a one-parameter read tool with annotations and no output schema, the description covers the input, the data source, the checks performed, and the return shape, which is sufficient to invoke it correctly. Only error/edge-case behavior (unsupported tokens, missing data) is unaddressed.

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 coverage is 100% and the single property is already documented as 'The SPL token mint address,' so the description's 'Pass the token MINT address' largely restates it. The capitalization reinforces that a mint, not a wallet or pool, is expected, but that is marginal added meaning over the schema.

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 specific verb and resource (risk screening for a Solana SPL token) and enumerates exactly what is checked: mint authority, freeze authority, closable/mutable metadata, transfer fees/hooks, holder and LP concentration. The 'Solana' qualifier plus the mint-address requirement distinguishes it from the EVM sibling without needing to name it.

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?

The closing sentence gives an explicit use case ('is this Solana token safe / a rug?'), which is a clear trigger condition. It stops short of exclusions or of naming token_risk_evm as the alternative for non-Solana tokens, so an agent must infer the chain boundary itself.

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.