Skip to main content
Glama

Arc sniper pnl

arc_sniper_pnl

Top Arc snipers and deployers ranked by realized on-chain USDC PnL ($0.009). $0.009 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": "arc_sniper_pnl"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 load and does disclose the critical behavior: this is a paid tool at $0.009 per call, payable via x402 in USDC on Arc/Base/Solana or XNT on X1, with a two-step quote-then-pay protocol. What it omits is the return shape of the ranked list, failure behavior on an invalid or expired payment, and any freshness or pagination characteristics.

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

Conciseness4/5

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

Three tight sentences: purpose first, then price, then the payment protocol. The price figure appears twice ('$0.009' inline and '$0.009 per call'), a small redundancy, but nothing else is wasted.

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

Completeness4/5

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

For a single-parameter paid ranking tool with no annotations and no output schema, the description covers purpose, price, payment rails, and the exact call protocol an agent must follow. The main remaining gap is that it never describes the response structure, which matters since no output schema exists.

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

Parameters4/5

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

Schema coverage is 100%, so the `payment` parameter is already documented, and with a single parameter the baseline is high. The description still adds real meaning by explaining the sequence — that omitting `payment` yields the terms, and passing it completes the purchase in the same call — which the schema alone does not convey.

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

Purpose4/5

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

The description names a specific resource and ordering metric: top Arc snipers and deployers ranked by realized on-chain USDC PnL. That is far more concrete than the bare name. It does not distinguish itself from nearby siblings such as arc_deployers or arc_creator_history, which an agent must disambiguate on its own.

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

Usage Guidelines4/5

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

It gives explicit procedural guidance: call once without `payment` to get the terms, sign with your own wallet, then call again with `payment` to complete the purchase. That is clear when-to-use guidance for the payment handshake. It gives no guidance on when to pick this tool over sibling analytics 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