Skip to main content
Glama
Sign In

Arcade.fun

by io.github.theguysaccount
OverviewDiscussionsAdmin

Create an experience

create_experience

Register a new experience and get its manage key. Returns game, key and the first version id. The key is shown only here and controls the listing forever — save it. This creates a draft; upload_build is what sends it for review.

Input Schema

NameRequiredDescriptionDefault
howNoHow to take part: the controls and how to begin.
kindNo'sdk' if the entry page calls arcade.ready(), otherwise 'web'. Detected from the build too.
emailYesReviewer contact address. Players never see it.
termsYesConfirm you agree to the arcade.fun terms and community guidelines.
titleYesWhat the experience is called, 2 to 60 characters.
aspectNoShape on screen. Empty fills the screen.
authorYesThe creator name players see, 2 to 30 characters.
inputsYesHow people interact. At least one.
rightsYesConfirm the experience is yours to share, including its art, music and code.
walletYesSolana address that receives this listing's creator trading fees. Every public listing launches with its own coin.
devicesNoDevices actually tested. Mobile requires touch, voice or camera among inputs.
taglineNoOne line for the cabinet.
releaseNotesNoPublic changelog notes, shown only after this build is approved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / releaseNotes
      Added value: +{
+  "additionalProperties": false,
+  "description": "Public changelog notes, shown only after this build is approved.",
+  "properties": {
+    "changes": {
+      "items": {
+        "maxLength": 240,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 12,
+      "minItems": 1,
+      "type": "array"
+    },
+    "title": {
+      "maxLength": 80,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "changes"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond annotations, it discloses that the returned manage key is shown only once and controls the listing forever, and that the call creates a draft rather than submitting for review. This is important behavioral context for a mutation tool; annotations already cover non-readonly/non-destructive status, though auth/rate-limit behavior is not described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action and return values, then the critical key warning, then the draft-vs-review distinction. Every sentence contributes necessary selection or handling information.

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 13-parameter mutation with no output schema, the description supplies the key return fields and warns about the one-time manage key, while the fully described schema covers parameter details. It is largely complete, though it omits failure/permission behavior and other sibling context.

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%, and the schema itself documents all 13 parameters including enums and nested releaseNotes. The description adds return-value context but no additional parameter semantics beyond what the schema provides, so baseline 3 applies.

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?

The description uses a specific verb and resource ('Register a new experience') and states the concrete outputs ('game, key and the first version id'). It also differentiates the draft-creation step from 'upload_build', so an agent can distinguish it from that sibling without opening the 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?

It clearly says this creates a draft and that 'upload_build is what sends it for review', giving an explicit alternative and condition. It does not cover other siblings such as start_version or list_experiences, so it stops short of full when/when-not guidance.

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