MCP server for sniping tokens on Raydium DEX across multiple regions with configurable parameters
Three tools with significant definition gaps. snipe_token accepts natural language input ('snipe XYZ with 2% slippage') but schema shows only string type with no format/pattern constraints, LLM cannot validate input. configure lacks descriptions for all four parameters (slippage, minProfit, maxGas, timeout); parameter names alone are ambiguous (e.g., is minProfit in SOL or percentage?). status has empty input schema but no output schema documented. No tool descriptions explain WHEN to use each tool or what they return. snipe_token marked IRREVERSIBLE but no confirmation/dry-run pattern implemented. Descriptions are present but generic (10-50 chars), below the 50-200 char baseline for LLM-optimized tools.
Configure sniper parameters
Snipe a token across multiple regions with specified parameters
Get current status of the sniper bot
configure tool has zero parameter descriptions. 'slippage', 'minProfit', 'maxGas', 'timeout' names alone do not clarify units, ranges, or constraints. LLM cannot validate input or understand side effects.
snipe_token accepts natural language input ('snipe XYZ with 2% slippage') but schema defines only string type with no format/pattern/enum. LLM cannot validate or constrain input; hallucinated values likely.
snipe_token marked IRREVERSIBLE but no dry-run, confirmation, or recovery pattern implemented. Agents cannot safely preview or undo token snipes.
status tool has empty input schema and no documented output schema. LLM cannot infer what fields to expect or how to use the response.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 36 | <=2025-11-25 | v2 |
Tool descriptions are 10-50 characters (below 50-200 char baseline). Descriptions lack WHEN/WHY context, prerequisites, or return value hints. LLM cannot distinguish tools or plan multi-step flows.