Skip to main content
Glama

Solana token full risk report (0.03 USDC, x402)

get_token_risk_report
Read-only

Rugsight full risk report for a Solana SPL / Token-2022 token: mint & freeze authority, Token-2022 extensions, top-20 holder breakdown (wallets vs pools/programs/burn), liquidity, main-pool LP burn/lock status (burnedPct, lockedPct, unlockAt), 24h volume, pool age, a launch-bundle / sniper heuristic for tokens up to 7 days old (very busy tokens may return status unknown), every risk flag explained, 0-100 score and A-F grade (or IC = issuer-controlled for allowlisted regulated assets such as USDC, PYUSD, cbBTC or xStocks), and whether on-chain metadata is mutable (informational; not scored). Costs 0.03 USDC on Solana per call, paid with x402: call without payment to receive the PaymentRequired object, then retry with _meta["x402/payment"].

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58)

Output Schema

NameRequiredDescriptionDefault
mintYes
nameNo
flagsYes
gradeYesA-F from the score; IC = issuer-controlled (allowlisted regulated/issuer asset)
scoreYes
issuerNo
marketNo
symbolNo
holdersNo
verdictNo
decimalsNo
metadataNoInformational only; does not change the score.
supplyUiNo
checkedAtNo
confidenceYes
disclaimerNo
extensionsNo
tokenProgramNo
mintAuthorityNo
technicalGradeNo
freezeAuthorityNo
authorityHoldersNo
issuerControlledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / metadata
      Added value: +{
      +  "description": "Informational only; does not change the score.",
      +  "properties": {
      +    "mutable": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "standard": {
      +      "enum": [
      +        "metaplex",
      +        "token2022",
      +        null
      +      ],
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "updateAuthority": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed6 schema fields changed
    • addedOutput schema / properties / authorityHolders
      Added value: +{
      +  "properties": {
      +    "freeze": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "mint": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / grade / description
      Added value: +"A-F from the score; IC = issuer-controlled (allowlisted regulated/issuer asset)"
    • changedOutput schema / properties / grade / enum
      Previous value: -[
      -  "A",
      -  "B",
      -  "C",
      -  "D",
      -  "F"
      -]New value: +[
      +  "A",
      +  "B",
      +  "C",
      +  "D",
      +  "F",
      +  "IC"
      +]
    • addedOutput schema / properties / issuer
      Added value: +{
      +  "properties": {
      +    "assetType": {
      +      "enum": [
      +        "stablecoin",
      +        "tokenized-stock",
      +        "wrapped-asset"
      +      ],
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "source": {
      +      "type": "string"
      +    }
      +  },
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / issuerControlled
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / technicalGrade
      Added value: +{
      +  "enum": [
      +    "A",
      +    "B",
      +    "C",
      +    "D",
      +    "F"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing the per-call price and currency, the exact x402 two-step payment handshake, the 'status unknown' degradation for very busy tokens in the launch-bundle heuristic, the IC grade path for allowlisted regulated assets (USDC, PYUSD, cbBTC, xStocks), and that on-chain metadata mutability is informational and not scored. These are exactly the behavioral traits an agent needs before spending money on a call.

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?

The payload list is front-loaded and every clause carries information an agent needs (scored vs informational fields, cost, payment flow). It is a single dense run-on sentence, which makes it slightly harder to scan than a bulleted structure, but there is essentially no filler to cut.

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?

An output schema exists, yet the description still sketches the shape of the result (scores, grades, flags, holder breakdown) and, critically, explains the paid-call protocol that no structured field covers. For a one-parameter, paid, read-only report tool, nothing an agent needs to call 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?

There is a single parameter (mint) with 100% schema description coverage and a base58 pattern, so the schema already carries the semantics. The description adds only indirect context (that the mint may be SPL or Token-2022), not format, normalization, or failure behavior for an invalid mint, so the baseline of 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 specific verb and resource ('full risk report for a Solana SPL / Token-2022 token') and then enumerates exactly what is covered: mint/freeze authority, Token-2022 extensions, top-20 holder breakdown, liquidity, LP burn/lock status, volume, pool age, bundle heuristic, flags, score/grade, and metadata mutability. That content list implicitly separates it from the sibling get_token_risk_score (which by name returns only the score), so an agent can choose without opening a schema.

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 description gives clear operational guidance for invocation (pay 0.03 USDC via x402, call without payment to get the PaymentRequired object, then retry with _meta["x402/payment"]) and notes a caveat for very busy/new tokens. However, it never states when to prefer this full report over the sibling get_token_risk_score, nor any when-not conditions, so the selection guidance is only implied by the enumerated payload.

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