Skip to main content
Glama
Sign In

Fivebar Trading

by io.github.fivebar-xyz
OverviewDiscussionsAdmin

Who sniped this launch?

snipe_check
Read-only

The snipers of a Solana token (pump.fun and other launches): the wallets besides the dev that bought in the block it launched or the few right after, and what kind each is. Tied to the dev: funded by the dev or by the wallet that funded the dev, or the dev paid for its buy (the dev taking supply under other names). Sniping bot: buys many different new tokens within seconds of launch (8 or more in its last 40 transactions), unrelated to the dev, usually selling within minutes. For each: share bought and held now, the Jito tip and fee it paid to land there, who funded it, whether it's a new wallet, and its recent trading. Use for 'who sniped this?', 'were the snipers the dev?', 'is this an insider launch or just bots?'. bundle_check covers everyone in the first minute. Facts, not an accusation. Premium: 2¢ a call from prepaid agent credits (3 free premium calls a day). Send your agent key as Authorization: Bearer .

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>"
    },
    "name": "snipe_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe token's Solana mint address
blocksNoBlocks after the launch block to include. Default 2 (about a second), max 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses the pricing model (2¢ per call, prepaid credits, 3 free premium calls/day), the required Authorization: Bearer header, and concrete detection thresholds (8+ of the last 40 transactions). It also frames output as 'Facts, not an accusation', which sets expectations about interpretation rather than asserting guilt.

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?

Front-loads the definition and classification rules, then use cases, then commercial terms — a sensible order. It is dense but almost every clause carries operational detail; minor slack in parentheticals like 'the dev taking supply under other names' and the closing disclaimer.

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

Completeness5/5

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

For a read-only, two-parameter tool with no output schema, the description covers what is returned per wallet (share bought/held, Jito tip and fee, funder, wallet age, recent trading), the classification logic, and the auth/payment requirements. Nothing an agent needs to call or interpret it correctly is missing.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented with defaults and max. The description's phrase 'the few right after' conveys the conceptual intent of the lookback window but never names the blocks parameter or discusses tradeoffs, so it does not meaningfully exceed the schema's own explanation.

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

Purpose5/5

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

Identifies the exact resource and scope: wallets other than the dev that bought in the launch block or immediately after, plus the classification of each (dev-tied vs sniping bot). It explicitly separates itself from bundle_check ('covers everyone in the first minute'), so an agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

Gives literal trigger questions ('who sniped this?', 'were the snipers the dev?', 'is this an insider launch or just bots?') and names the adjacent tool plus the boundary that selects it. Nothing about when-to-use is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fivebar Trading toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources