Agent Data API

solana_token_snapshot

Rug check and due-diligence snapshot of a Solana SPL or Token-2022 token: a 0-100 risk score with reasons, name, symbol, supply, mint and freeze authority, Token-2022 controls (permanent delegate, transfer fees, transfer hook, pausable), metadata mutability, top-holder concentration split into wallets and program accounts, and USD price, liquidity, volume and pools from Jupiter and DexScreener. Facts only, no buy or sell opinion. Costs $0.01 USDC on Base via x402.

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": {
      "address": "<address>"
    },
    "name": "solana_token_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Token mint address on Solana (base58)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the result is a read-only factual snapshot, not investment advice, and that invocation costs $0.01 USDC on Base via x402. It does not explicitly discuss permissions or rate limits, but the key behavioral traits are covered.

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 description is front-loaded with the core purpose and packs a large amount of relevant output detail into a dense single sentence. It earns most of its length, though the long enumerations make it slightly harder to scan quickly.

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, but the description fully enumerates what the snapshot returns: risk score, token metadata, authorities, Token-2022 controls, holder concentration, and Jupiter/DexScreener market data. For a single-parameter read tool, this is complete enough for an agent to know exactly what to expect.

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 the sole address parameter as a base58 Solana token mint address with a pattern constraint. The description adds context that the tool covers SPL and Token-2022 tokens, but it does not add syntax or format details beyond 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?

The description states a specific verb and resource: a rug-check/due-diligence snapshot for Solana SPL and Token-2022 tokens. It enumerates the exact outputs (risk score, authorities, Token-2022 controls, holder concentration, market data), making the tool clearly distinguishable from sibling token snapshots on other chains and from wallet tools.

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?

It clearly conveys the intended use case: due diligence and rug checking, with facts only and no buy/sell opinion. However, it does not explicitly name when to use this instead of overlapping siblings such as token_risk_check, so the routing guidance is clear but not exhaustive.

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

All Agent Data API 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?