Skip to main content
Glama

Trading Signals Toolkit

Solana Token Verdict

solana_token_verdict
Read-only

Call before an agent buys or accepts a Solana SPL or Token-2022 mint (memecoins, pump.fun launches, airdrops). Returns safe / caution / avoid plus an A-F grade with plain reasons: mint and freeze authority, Token-2022 traps (transfer fee, hook, permanent delegate), liquidity across DEXes and LP lock/burn, a live ~$1k sell test, top-10 holders, creator holdings and launch count, and linked insider (sniper/bundle) wallets. Not a security audit. Read-only, never places orders. Informational only, not investment advice.

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58), e.g. DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263 for BONK

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces that ('Read-only, never places orders') while adding real context beyond the flags: the verdict vocabulary, the A-F grading, the specific on-chain checks performed, and a live sell test. The 'live ~$1k sell test' is a server-side simulation whose cost or latency implications are not explained, which is the main remaining gap.

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 when-to-call instruction is front-loaded, followed by an enumerated list of checks, which is easy to scan. The tail contains mild redundancy ('Read-only, never places orders', 'Informational only, not investment advice', 'Not a security audit'), but those disclaimers serve a real purpose for an agent deciding whether to rely on the result.

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?

With no output schema, the description competently substitutes by describing verdict categories, grade, and the evidence behind them, so an agent knows what it will receive. It never mentions latency or cost despite the live sell test, which an agent planning a trade sequence would want to know.

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, including a base58 pattern and a worked example (BONK), so the schema carries the semantics. The description adds nothing parameter-specific beyond the base58 format already documented, which is the expected baseline here.

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 uses a specific verb and resource ('Call before an agent buys or accepts a Solana SPL or Token-2022 mint') and enumerates exactly what it checks and returns (authorities, Token-2022 traps, liquidity, sell test, holders, insiders). It does not explicitly distinguish itself from nearby siblings such as token_pre_trade or pre_trade_check, so an agent must infer the boundary rather than being told it.

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 gives a clear trigger condition up front: call this before buying or accepting a mint, with concrete examples (memecoins, pump.fun launches, airdrops). It also scopes expectations with 'Not a security audit' and 'Informational only'. It stops short of naming an alternative tool or stating when not to call it.

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