Skip to main content
Glama

My MCP Server

flash-loan-arbitrage

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

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It discloses only that it runs on live Mainnet and costs $0.10 USDC via an x402 v2 PAYMENT-SIGNATURE header — useful payment/auth context, but silent on whether it executes irreversible on-chain trades, what happens to funds, failure modes, or rate limits.

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?

It is short, but the brevity is under-specification rather than economy: the only content is a price/payment note, with the actual operation left unexplained.

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?

For a live-funds, payment-gated operation with no annotations, no output schema, and fully undocumented parameters, the description omits nearly everything an agent needs: what is executed, expected inputs, and side effects.

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 two parameters (mint, targetWallet), and the description never mentions either. Neither name nor meaning is clarified anywhere, leaving the agent to guess the expected formats and roles.

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 ('flash-loan-arbitrage' on 'Solana Mainnet') without stating what the tool actually does — whether it executes an arbitrage trade, returns opportunities, or quotes a route. An agent cannot distinguish it from siblings like mev-arbitrage-bot or cross-dex-router based on this text.

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?

There is no when-to-use or when-not-to-use guidance. Nothing indicates the preconditions for calling it (wallet funding, payment, network state) or why an agent would pick it over the many sibling arbitrage/sniper tools.

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