Skip to main content
Glama
Sign In

Fivebar Trading

by io.github.fivebar-xyz
OverviewDiscussionsAdmin

What's launching now: ticker waves and copycats

copycat_radar
Read-only

New tokens launched on Robinhood Chain in the last hours (default 6, up to 72), read from the chain within minutes: how many and how fast against the window before, waves of new tokens sharing one ticker (how many copies, how many different launchers, when the wave started, and which copy has the most liquidity now), the wallets launching the most, and the contracts most launches go through. Pass symbol for one ticker's copies in the window, each with its launcher and liquidity now. Use for 'what's launching?', 'what's trending on Robinhood Chain?', 'how many CLAUS clones are there?', 'is this the real one?'. A ticker is not an identity. From Fivebar's launch index of every Uniswap v3 and v4 pool on Robinhood Chain.

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

Input Schema

NameRequiredDescriptionDefault
minNoNew tokens with one ticker that make a wave, default 3
hoursNoWindow in hours, default 6, max 72
symbolNoOptional: one ticker, to list its copies

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds valuable context on data source (Fivebar launch index, Uniswap v3/v4 pools), freshness ('within minutes'), and window bounds. It also warns 'A ticker is not an identity,' which is a genuinely useful behavioral caveat. However, it says nothing about result caps, rate limits, or how many rows come back, which matters for an open-world aggregate query.

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?

Purpose is front-loaded, but the core is a single dense run-on sentence with a long parenthetical enumerating wave fields. The hours default and max are restated from the schema, which is mild redundancy, and the flow would be easier to parse if the wave breakdown were a separate clause or list.

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?

With no output schema, the description carries the return-shape burden and does describe the aggregates (counts, speed vs. prior window, copy/wave stats, top launchers, top contracts) plus the symbol-mode payload. Missing only secondary details such as result limits and ordering.

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 baseline is 3, but the description adds meaning: min defines a 'wave' of copies sharing a ticker, hours is the comparison window against the prior period, and symbol returns each copy with its launcher and current liquidity. That goes beyond the terse schema text.

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?

States a specific analysis verb set and resource: new token launches on Robinhood Chain, ticker waves, copy counts, launchers, and contracts. The scope ('read from the chain within minutes', 'Fivebar's launch index of every Uniswap v3 and v4 pool') clearly separates it from generic token or snipe-checking siblings.

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?

Provides concrete trigger phrases ('what's launching?', 'how many CLAUS clones are there?', 'is this the real one?') and explains that passing symbol switches to a single-ticker copy listing. It never states when NOT to use it or names an alternative tool, so it stops short of full routing guidance.

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