Solana Wallet Intel

token_check_demo

Read-onlyIdempotent

Free demo. Try free, then pay per call. Pass one Solana token mint and get a real rug-check: riskScore, riskLevel, a one-line verdict, the top risk flags, liquidity, market cap, age, and pump.fun status. Uses free public data only. Cached 60 seconds per mint and rate-limited to 20 calls a minute per client. The paid routes return every flag, the full on-chain checks, and wallet intelligence.

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

Input Schema

Name	Required	Description	Default
`mint`	Yes	Solana token mint in base58 (32 to 44 characters). Invalid mints return HTTP 400. This route is free.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), it discloses concrete operational traits: 60-second per-mint caching, a 20 calls/minute per-client rate limit, free public data only, and that the payload is a truncated subset of the paid response. That is exactly the kind of behavior an agent needs to avoid surprise.

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?

Dense and front-loaded with the free-demo and return-content facts first, then operational limits. The 'Try free, then pay per call' framing is mildly promotional but still conveys the tiering; no sentence is truly wasted.

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?

There is no output schema, so the description carrying the return-field list, data-source limits and the paid-tier delta is essential and fully covers what an agent needs before calling this single-parameter tool.

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 schema already documents base58 format, length, and the HTTP 400 behavior for invalid mints. The description only adds that you pass one mint, which is a baseline-3 contribution when the schema does the heavy lifting.

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: pass one Solana token mint and get a rug-check, enumerating exactly what is returned (riskScore, riskLevel, verdict, flags, liquidity, market cap, age, pump.fun status). This is clearly distinguishable from the wallet_* siblings and token_trending.

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?

Establishes the context clearly: it is a free demo route, and the paid routes return every flag, full on-chain checks and wallet intelligence, which tells the agent when this limited route is or isn't sufficient. It does not name specific sibling tools to route to, so it falls short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Solana Wallet Intel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?