Skip to main content
Glama
Sign In

Arcade.fun

by io.github.theguysaccount
OverviewDiscussionsAdmin

Add an optional creator payout address

set_creator_wallet
Idempotent

Set an address once on a wallet-free listing you own, if the creator wants an optional coin. It receives the creator's share of trading fees and cannot be changed later, so use the creator's own address. No wallet signature, market launch or payment. Afterwards, coin_launch_link gives the creator a link to launch the coin.

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>",
      "wallet": "<wallet>"
    },
    "name": "set_creator_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
gameYes
walletYesOptional Solana payout address for an optional future coin. Omit for a free listing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true) it discloses the critical non-obvious trait: the address is permanent and cannot be changed later, and it receives the creator's fee share. It also rules out wallet signature, market launch, and payment side effects, which materially reduces agent hesitation. It does not describe the failure mode when a second, different address is attempted.

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?

Four tight sentences, front-loaded with the action and its precondition, then the immutability warning, then the no-side-effect assurance, then the next tool. The telegraphic 'No wallet signature, market launch or payment' is slightly compressed but still parseable.

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

Completeness3/5

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

The workflow context is well covered (permanence, no signature, follow-up link), which is the main risk area for this mutation. But with 33% schema coverage there is a real hole: two required identifying parameters are never explained, and an agent cannot verify that it is targeting the right listing.

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?

Only 'wallet' is documented (in the schema), and the description adds useful guidance there: use the creator's own address, since it collects trading fees permanently. However, 'game' and 'key' — two of three required parameters — are undocumented in both schema and description; 'listing you own' implies they identify the listing, but an agent gets no indication of which is which or what format each takes.

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 gives a specific verb and resource ('Set an address once on a wallet-free listing you own') and scopes it to the optional-coin case, so it is clearly not set_cover or set_entry. It stops short of explicitly contrasting with the sibling that handles already-wallet-enabled listings, but the object it acts on is unambiguous.

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 states the precondition (wallet-free listing you own), the intent condition (creator wants an optional coin), and the one-time nature, plus points to coin_launch_link as the follow-up step. It does not say what to do if the listing already has a wallet or how to check that beforehand.

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