Skip to main content
Glama

My MCP Server

limit-order-sniper

Live Solana Mainnet limit-order-sniper ($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": "limit-order-sniper"
  }
}

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 carries the full behavioral burden. It does disclose one genuinely useful trait — a $0.10 USDC charge via an x402 v2 PAYMENT-SIGNATURE header — but says nothing about whether the tool executes trades, spends funds, is idempotent, or what it returns.

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 a single short phrase with no wasted sentences, and the environment/pricing detail is front-loaded. However, the terseness reflects under-specification rather than economy — nothing about invocation or effect is conveyed.

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 tool that appears to act on live mainnet funds with two undocumented parameters, no annotations, and no output schema, the definition supplies almost nothing. An agent cannot determine what the tool will do, what it costs beyond the listed fee, or what happens to the caller's assets.

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

Parameters2/5

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

Schema description coverage is 0% and the description does not mention the two parameters (mint, targetWallet) at all. An agent must infer that 'mint' is likely an SPL token mint and 'targetWallet' a wallet to watch, with no format, requiredness, or behavioral meaning supplied.

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 description is essentially the tool name restated with environment and pricing appended: 'limit-order-sniper' on Solana Mainnet. It never states a verb or what the tool actually does (place an order? watch the mempool? execute a swap?), so an agent cannot distinguish its behavior from siblings like 'solana-sniper-daemon' or 'mev-arbitrage-bot'.

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 versus any alternative, no preconditions, and no exclusions. The only contextual detail is the price, which does not help an agent decide when this tool is the right choice.

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