Skip to main content
Glama

Solana token risk score (free)

get_token_risk_score
Read-only

Free basic risk score for a Solana token: 0-100 score, A-F grade (or IC for allowlisted issuer-controlled assets), verdict, risk flag codes, and whether on-chain metadata is mutable (informational; not scored). Free, no payment needed.

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_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58)

Output Schema

NameRequiredDescriptionDefault
mintYes
flagsNo
gradeYes
scoreYes
issuerNo
verdictNo
metadataNoInformational only; does not change the score. Metaplex is_mutable and update authority, or Token-2022 metadata / metadata-pointer authority.
checkedAtNo
confidenceNo
disclaimerNo
fullReportNo
liquidityLockNo
technicalGradeNo
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. Metaplex is_mutable and update authority, or Token-2022 metadata / metadata-pointer authority.",
      +  "properties": {
      +    "mutable": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "standard": {
      +      "enum": [
      +        "metaplex",
      +        "token2022",
      +        null
      +      ],
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "updateAuthority": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • addedOutput schema / properties / disclaimer
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / fullReport
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / liquidityLock
      Added value: +{
      +  "properties": {
      +    "burnedPct": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "lockedPct": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "poolType": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "reason": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "type": "string"
      +    },
      +    "unlockAt": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  3. Changed4 schema fields changed
    • 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"
      +}
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new context — that there is no cost, that grading uses an A-F scale with a special IC case for allowlisted issuer-controlled assets, and that metadata mutability is reported but explicitly not scored. Missing are error cases (invalid/non-existent mint) and the fact that scores are a snapshot with no staleness guarantee.

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?

One dense, front-loaded sentence that packs the output surface and the cost model without filler. The trailing "Free, no payment needed" is slightly redundant with "Free basic" at the start but is defensible as emphasis.

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 previews the return shape well enough for an agent to decide relevance, and it covers cost and the IC grading exception. For a read-only single-parameter lookup, nothing essential to calling 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?

Schema coverage is 100% with a single required parameter, so the schema fully documents the base58 mint address and its pattern. The description adds nothing beyond identifying the input as a Solana token, which is baseline for a one-parameter tool.

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?

The description names a specific verb and resource ("risk score for a Solana token") and enumerates the returned fields — 0-100 score, A-F grade, verdict, risk flag codes, metadata mutability. The words "free basic" implicitly signal a tier below the sibling get_token_risk_report, though the sibling is never named, so the differentiation is inferred rather than stated.

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?

It states this is free and requires no payment, which is a real selection signal, but it never says when to prefer it over get_token_risk_report or what that other tool adds. Usage is only implied by the word "basic."

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