Skip to main content
Glama

My MCP Server

raydium-swap-automator

Live Solana Mainnet raydium-swap-automator ($0.10 USDC via x402 v2 PAYMENT-SIGNATURE header)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "raydium-swap-automator"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose one genuinely valuable behavioral fact -- the tool is paid ($0.10 USDC) and requires an x402 v2 PAYMENT-SIGNATURE header -- but says nothing about whether it signs and submits a live transaction, what permissions or wallet it needs, slippage handling, or irreversibility of a mainnet swap.

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

Conciseness3/5

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

It is short and the network and payment facts are up front, so nothing is bloated. However it reads as a title fragment rather than structured sentences, and the space saved is squandered on under-specification rather than efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a mainnet financial-execution tool with two undocumented parameters, no annotations, and no output schema; the description supplies none of the safety, prerequisite, or parameter information an agent needs to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters. The description does not mention 'mint' or 'targetWallet' at all, leaving the agent with no notion of expected formats (mint address vs symbol) or what the target wallet is used for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text largely restates the tool name ("raydium-swap-automator") and adds only that it runs on Solana Mainnet. It never states a verb or what the tool actually does -- execute a swap? build a transaction? return a quote? An agent cannot confidently distinguish it from siblings like cross-dex-router or flash-loan-arbitrage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool, when not to, or which sibling to prefer. The only constraint-like content is pricing, which does not help an agent choose between swap/routing alternatives.

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