Fivebar Trading

Was the launch bundled?

bundle_check

Read-only

Who bought a token in the first 60 seconds after trading opened: how many wallets, what share of supply they took and still hold, how many bought in the very block trading opened, and which early buyers are linked to each other or to the dev. 0x tokens on Robinhood Chain, Ethereum or Base (pass chain, or it finds it): linked means they moved the token between them. Also takes a Solana mint (pump.fun and other launches): there, linked also means funded by the same wallet shortly before buying, funded by the dev, bought in one transaction or paid each other's fees, and it says how many of the biggest buyers were brand-new wallets. On Solana, earlyBought counts every buy (fast in-and-out trading can push it past 100%); heldAtWindowEnd is what they still held when the window closed. Use for 'is this bundled?', 'was the launch sniped?'. 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": "bundle_check"
  }
}

Input Schema

Name	Required	Description
`chain`	No	For a 0x address: the chain. Default: Robinhood Chain if the token is there, else Ethereum, else Base
`token`	Yes	Token contract address (0x...) on Robinhood Chain, Ethereum or Base, or a Solana mint
`seconds`	No	Early window after trading opened, in seconds. Default 60, max 600

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

addedInput schema / properties / chain

Added value: +{
+  "description": "For a 0x address: the chain. Default: Robinhood Chain if the token is there, else Ethereum, else Base",
+  "enum": [
+    "robinhood",
+    "ethereum",
+    "base"
+  ],
+  "type": "string"
+}

changedInput schema / properties / token / description

Previous value: -"Token contract address (0x...) on Robinhood Chain, or a Solana mint"New value: +"Token contract address (0x...) on Robinhood Chain, Ethereum or Base, or a Solana mint"

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / token / description

Previous value: -"Token contract address (0x...) on Robinhood Chain"New value: +"Token contract address (0x...) on Robinhood Chain, or a Solana mint"

AddedNov 1, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context beyond them: prepaid pricing (2¢/call, 3 free premium calls daily) and the Authorization: Bearer key requirement. It also discloses metric quirks (on Solana earlyBought counts every buy and can exceed 100%; heldAtWindowEnd is the residual at window close) and the chain auto-detection fallback order, which are useful behavioral details not present in the annotations.

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?

The purpose is front-loaded, but the body is a dense run-on of parenthetical asides, and the Solana behavior is spread across three sentences with repeated framing ("Also takes a Solana mint", "On Solana..."). The pricing and auth notice is tacked onto the end rather than separated into its own structural block.

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 multi-chain tool with no output schema, it covers the essentials: what the returned metrics mean on each chain, what "linked" means per chain, the window semantics, and the credential/payment requirement. The remaining gap is return shape and ordering/capping of the early-buyer list, which an agent would only discover by calling it.

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 description coverage is 100%, so all three parameters are already documented, including the chain default resolution order and the seconds default/max. The description's "pass chain, or it finds it" and its Solana-mint note restate the schema rather than adding new parameter-level meaning, so the baseline of 3 applies.

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 opening sentence states a specific verb and resource: who bought a token in the first 60 seconds after trading opened, with concrete outputs (wallet count, supply share held, same-block buys, buyer links). It never names a sibling to distinguish itself from, so an agent must infer the boundary with snipe_check, token_holders and dev_check 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 trigger phrases ("is this bundled?", "was the launch sniped?") and branches guidance by input type: 0x tokens on three chains vs a Solana mint, with different definitions of "linked" for each. There is no when-not guidance and no named alternative, so the routing signal is clear but not exclusive.

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

All Fivebar Trading tools Inspect

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.