Skip to main content
Glama
Sign In

PnL Labs — Solana Trust & Risk Checks

by io.github.PnLlabs
OverviewDiscussionsAdmin

Check Token Structural Risk

check_token_safety
Read-onlyIdempotent

Analyzes structural risk of a Solana token from on-chain data: real-holder concentration with bonding-curve and liquidity-pool accounts excluded, presence of known sniper-bot addresses among early buyers, and a simulated buy/sell round trip to detect honeypot behavior. Returns: verdict (LOW_RISK, ELEVATED, HIGH_RISK, CRITICAL, UNKNOWN), stable reason codes, and top-holder percentages. Scope is structural only; it does not detect risk that exists purely in trading behavior.

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58, 32-44 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mint / description
      Previous value: -"Solana token mint address (base58)"New value: +"Solana token mint address (base58, 32-44 chars)"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnly/openWorld/idempotent annotations, description discloses methodology (excludes bonding-curve/LP accounts, simulates buy/sell) and output components (verdict, reason codes, percentages). It also notes limitation about trading-behavior risk.

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?

Three sentences, front-loaded with the main purpose, then outputs, then scope. No wasted words; each sentence adds essential information.

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?

For a single-param tool with no output schema, description covers behavior, outputs, and limitations well. No significant gaps.

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 already provides 100% description coverage for mint (base58, 32-44 chars), and the description does not add parameter-specific detail. Baseline 3 is appropriate.

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?

Description uses specific verb 'Analyzes structural risk of a Solana token from on-chain data', lists concrete components (holder concentration, sniper bots, honeypot simulation). Clearly distinguishes from sibling wallet/trade cost tools by focusing on token structural risk.

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?

States clear scope ('structural only') and what it does NOT detect ('trading behavior'), which helps choose when to use it. However, it does not explicitly mention alternatives like check_wallet_forensics or check_trade_cost, so it earns a 4 rather than 5.

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

All PnL Labs — Solana Trust & Risk Checks toolsInspect
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