Skip to main content
Glama

My MCP Server

mev-arbitrage-bot

Live Solana Mainnet mev-arbitrage-bot ($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": "mev-arbitrage-bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a genuinely useful behavioral trait: the endpoint is paywalled at $0.10 USDC via an x402 v2 PAYMENT-SIGNATURE header, which tells an agent about auth and cost. However, it says nothing about whether the tool executes on-chain trades (irreversible, fund-spending), what it returns, or what happens when the optional parameters are omitted.

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?

A single short front-loaded string with no wasted prose, but it reads like a listing title rather than a structured definition; the parenthetical payment clause is jammed in without clarifying the operation.

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

Completeness2/5

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

For a financially consequential tool with zero annotations, no output schema, and two fully undocumented parameters, the description is far too thin. The payment disclosure helps, but nothing explains execution semantics, risk, or return values.

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 (mint, targetWallet), and the description never mentions them. An agent must guess the format of mint (address? symbol?) and the meaning of targetWallet, including whether either is required.

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 ('mev-arbitrage-bot') and adds only network context ('Live Solana Mainnet') plus a price. There is no verb stating what the tool actually does — scans for opportunities, executes trades, or returns routes — so an agent cannot distinguish it from flash-loan-arbitrage or cross-dex-router.

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

Usage Guidelines2/5

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

No when-to-use guidance and no named alternatives among the many arbitrage/routing siblings. The only contextual signal is the payment requirement, which is a precondition, not usage guidance.

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