Skip to main content
Glama

solana_token_risk_scan

Read-onlyIdempotent

Solana token rug check: mint/freeze authority, holder concentration, liquidity depth, and a composite 0-100 risk score. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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

Input Schema

NameRequiredDescriptionDefault
mintYesBase58 Solana token mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description's job is to add context, and it does: it discloses the free tier of 10 calls per day and, critically, that beyond that limit the response changes to a pay-per-call x402 endpoint plus price rather than a scan result. That is exactly the kind of behavioral surprise an agent needs warned about; only the failure mode for malformed mints and the exact output shape are left unstated.

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?

Two sentences, zero waste, and the substantive content (what is checked and the resulting score) is front-loaded before the billing caveat. Every clause earns its place.

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-only tool with full annotation coverage and no output schema, the definition gives enough to call it correctly and to anticipate the quota-related response change. It stops short of describing the return fields (e.g., per-factor pass/fail vs numeric) or error behavior, which would make it fully self-contained.

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 required parameter with 100% schema description coverage ('Base58 Solana token mint address'), so the schema carries the semantics. The description adds nothing about the mint parameter — no format examples, no guidance on where to source a valid mint address — which is acceptable but not additive.

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 states a specific resource and check ('Solana token rug check') and enumerates exactly what is inspected: mint/freeze authority, holder concentration, liquidity depth, plus a composite 0-100 score. It does not name the nearest sibling (token_risk_metrics, token_intel, token_compare), so an agent must infer the boundary from scope alone, which keeps it below a 5.

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?

Usage is only implied: the framing 'rug check' signals a pre-trade due-diligence call, and the quota sentence hints at volume constraints. There is no explicit when-to-use, when-not-to-use, or pointer to token_risk_metrics / wallet_safety / risk_batch for related questions.

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.