Skip to main content
Glama
Sign In

Arcade.fun

by io.github.theguysaccount
OverviewDiscussionsAdmin

Get a link the creator opens to launch the game's coin

coin_launch_link

For a live listing with a payout wallet: returns a 24-hour link that can do one thing, launch this game's optional coin. Give it to the creator. They open it in a browser with that Solana wallet (on a phone it opens inside Phantom, Solflare or Backpack), press Launch and approve in the wallet; it costs them about 0.0085 SOL and they earn 40% of every trading fee. You cannot launch the coin yourself: it needs the creator wallet's signature. The link cannot change the listing, and a new link retires the old one.

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": {
      "game": "<game>",
      "key": "<key>"
    },
    "name": "coin_launch_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
gameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: 24-hour expiry, a new link retiring the old one, the ~0.0085 SOL cost to the creator, the 40% fee share, that the link cannot modify the listing, and the wallet environments it opens in. These are exactly the operational facts an agent needs to explain the tool's effect to a user.

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?

Purpose and prerequisites are front-loaded, and nearly every clause carries information (expiry, cost, fee share, signature requirement, link rotation). The middle sentence listing three wallet apps is a slight digression and the paragraph runs long, but nothing is padding.

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 link-generating tool with no output schema, the description covers when it applies, who consumes the link, what happens on click, cost, and link invalidation. The remaining gaps are the unexplained 'key' parameter and the absence of any hint about the returned link's format.

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 coverage is 0% for two required parameters. The description implies 'game' identifies the game/listing, but 'key' is never explained — whether it is a listing key, payout wallet key, or idempotency token is left entirely to inference. With no schema descriptions to fall back on, this is a real gap.

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 verb and resource — returns a 24-hour link that launches this game's coin — and immediately scopes it to 'a live listing with a payout wallet.' An agent can distinguish this from siblings like create_experience or start_version without opening any schema.

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?

Preconditions are explicit (live listing, payout wallet present) and the handling instruction is unambiguous: 'Give it to the creator.' It also states a hard limit — 'You cannot launch the coin yourself: it needs the creator wallet's signature' — which is effectively a when-not-to-try rule. It does not name a sibling alternative, which keeps it just short of a 5.

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

All Arcade.fun 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