Skip to main content
Glama
Sign In

x402-solana

by io.github.digitalweb33333-creator
OverviewDiscussionsAdmin

solana_pre_trade

All-in-one Solana pre-trade decision in ONE call: BUY-SAFE/CAUTION/AVOID fusing four scored modules — token security, EXECUTABLE liquidity depth (estimated slippage at $100/$1k/$10k), deployer history/control and holder concentration. Should I buy or avoid this Solana token? Full token due-diligence in one call — replaces 3-4 lookups; built for a trading / sniping agent's risk-review pipeline. Solana trading safety decision and buy/avoid verdict. Price: $0.05 per call (x402 payment, USDC on Base mainnet).

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

Input Schema

NameRequiredDescriptionDefault
mintYesSPL token mint address (base58) to evaluate before buying

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden. It discloses the cost ($0.05 per call with x402 payment) and the modules involved, but it does not explicitly state that it is read-only or that no on-chain transaction occurs. It provides some behavioral context but lacks details on side effects, rate limits, or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is repetitive, restating 'in ONE call' and 'buy/avoid' multiple times. It is longer than necessary and contains marketing-style phrasing that could be condensed without losing meaning.

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?

Given the simple input (one param), the description is fairly complete: it explains the modules, the verdict categories, the target use case, and the cost. It does not detail the output structure, but the absence of an output schema makes the description's mention of the verdict categories adequate.

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?

The input schema has 100% coverage for the mint parameter, so the baseline is 3. The description adds only that the tool evaluates a Solana token, but does not provide additional syntax, format, or examples beyond what the schema already documents.

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 clearly states the tool's purpose: an all-in-one Solana pre-trade decision tool that outputs BUY-SAFE/CAUTION/AVOID verdicts by fusing four scored modules. It explicitly positions itself against sibling tools by claiming to replace 3-4 lookups and being built for trading/sniping risk-review.

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?

The description provides clear usage context: it is for pre-trade decisions and suitable for a trading/sniping agent's risk-review pipeline. It implies when to use (before buying a Solana token) and argues it replaces multiple lookups, though it does not explicitly name alternative tools or edge cases where it should not be used.

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

All x402-solana 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