Playgama MCP - Publish & Manage HTML5 Games

Create a game

create_application

Destructive

Create a draft game. Answers its id, which the other tools take. Titles are not unique: if a call failed without a clear answer, check list_applications before creating again.

Input Schema

TableJSON Schema

Name	Required	Description
`agent`	No	The coding agent the game was made with: claude-code (Claude Code), codex (Codex), cursor (Cursor), antigravity (Google Antigravity), opencode (OpenCode), gemini-cli (Gemini CLI), kimi-code (Kimi Code Agent), grok-build (Grok Build), workbuddy (WorkBuddy), zcode (ZCode), claude-app (Claude app (chat / Desktop)), chatgpt (ChatGPT (chat)), other (Other), none (No AI agent)
`model`	No	The model behind that agent: claude-fable (Claude Fable), claude-opus (Claude Opus), claude-sonnet (Claude Sonnet), claude-haiku (Claude Haiku), openai-astra (OpenAI Astra), openai-sol (OpenAI Sol), openai-luna (OpenAI Luna), openai-terra (OpenAI Terra), gemini-pro (Gemini Pro), gemini-flash (Gemini Flash), grok (Grok), kimi (Kimi), qwen (Qwen), deepseek (DeepSeek), glm (GLM), other (Other)
`title`	Yes	The game’s title in English — Latin letters, digits, spaces and punctuation, up to 120 characters. Shown to players and moderators as-is.
`engine`	Yes	The engine the game was built with: unity (Unity), construct3 (Construct 3), cocos-creator (Cocos Creator), defold (Defold), godot (Godot), gdevelop (GDevelop), game_maker (Game Maker), scratch (Scratch), js (plain JavaScript, no engine)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026

changedInput schema / properties / agent / description

Previous value: -"The coding agent the game was made with: claude-code (Claude Code), codex (Codex), cursor (Cursor), kimi-code (Kimi Code Agent), grok-build (Grok Build), workbuddy (WorkBuddy), other (Other), none (No AI agent)"New value: +"The coding agent the game was made with: claude-code (Claude Code), codex (Codex), cursor (Cursor), antigravity (Google Antigravity), opencode (OpenCode), gemini-cli (Gemini CLI), kimi-code (Kimi Code Agent), grok-build (Grok Build), workbuddy (WorkBuddy), zcode (ZCode), claude-app (Claude app (chat / Desktop)), chatgpt (ChatGPT (chat)), other (Other), none (No AI agent)"

changedInput schema / properties / agent / enum

Previous value: -[
-  "claude-code",
-  "codex",
-  "cursor",
-  "kimi-code",
-  "grok-build",
-  "workbuddy",
-  "other",
-  "none"
-]New value: +[
+  "claude-code",
+  "codex",
+  "cursor",
+  "antigravity",
+  "opencode",
+  "gemini-cli",
+  "kimi-code",
+  "grok-build",
+  "workbuddy",
+  "zcode",
+  "claude-app",
+  "chatgpt",
+  "other",
+  "none"
+]

changedInput schema / properties / model / description

Previous value: -"The model behind that agent: claude-fable (Claude Fable), claude-opus (Claude Opus), claude-sonnet (Claude Sonnet), claude-haiku (Claude Haiku), openai-astra (OpenAI Astra), openai-sol (OpenAI Sol), openai-luna (OpenAI Luna), openai-terra (OpenAI Terra), grok (Grok), kimi (Kimi), other (Other)"New value: +"The model behind that agent: claude-fable (Claude Fable), claude-opus (Claude Opus), claude-sonnet (Claude Sonnet), claude-haiku (Claude Haiku), openai-astra (OpenAI Astra), openai-sol (OpenAI Sol), openai-luna (OpenAI Luna), openai-terra (OpenAI Terra), gemini-pro (Gemini Pro), gemini-flash (Gemini Flash), grok (Grok), kimi (Kimi), qwen (Qwen), deepseek (DeepSeek), glm (GLM), other (Other)"

changedInput schema / properties / model / enum

Previous value: -[
-  "claude-fable",
-  "claude-opus",
-  "claude-sonnet",
-  "claude-haiku",
-  "openai-astra",
-  "openai-sol",
-  "openai-luna",
-  "openai-terra",
-  "grok",
-  "kimi",
-  "other"
-]New value: +[
+  "claude-fable",
+  "claude-opus",
+  "claude-sonnet",
+  "claude-haiku",
+  "openai-astra",
+  "openai-sol",
+  "openai-luna",
+  "openai-terra",
+  "gemini-pro",
+  "gemini-flash",
+  "grok",
+  "kimi",
+  "qwen",
+  "deepseek",
+  "glm",
+  "other"
+]

Changed4 schema fields changedSep 23, 2026

changedInput schema / properties / agent / description

Previous value: -"The coding agent the game was made with: claude-code (Claude Code), codex (Codex), cursor (Cursor), other (another agent), none (no agent, written by hand)"New value: +"The coding agent the game was made with: claude-code (Claude Code), codex (Codex), cursor (Cursor), kimi-code (Kimi Code Agent), grok-build (Grok Build), workbuddy (WorkBuddy), other (Other), none (No AI agent)"

changedInput schema / properties / agent / enum

Previous value: -[
-  "claude-code",
-  "codex",
-  "cursor",
-  "other",
-  "none"
-]New value: +[
+  "claude-code",
+  "codex",
+  "cursor",
+  "kimi-code",
+  "grok-build",
+  "workbuddy",
+  "other",
+  "none"
+]

changedInput schema / properties / model / description

Previous value: -"The model family behind that agent: claude (Claude), gpt (GPT), gemini (Gemini), other (another model)"New value: +"The model behind that agent: claude-fable (Claude Fable), claude-opus (Claude Opus), claude-sonnet (Claude Sonnet), claude-haiku (Claude Haiku), openai-astra (OpenAI Astra), openai-sol (OpenAI Sol), openai-luna (OpenAI Luna), openai-terra (OpenAI Terra), grok (Grok), kimi (Kimi), other (Other)"

changedInput schema / properties / model / enum

Previous value: -[
-  "claude",
-  "gpt",
-  "gemini",
-  "other"
-]New value: +[
+  "claude-fable",
+  "claude-opus",
+  "claude-sonnet",
+  "claude-haiku",
+  "openai-astra",
+  "openai-sol",
+  "openai-luna",
+  "openai-terra",
+  "grok",
+  "kimi",
+  "other"
+]

Changed2 schema fields changedSep 22, 2026

addedInput schema / properties / agent

Added value: +{
+  "description": "The coding agent the game was made with: claude-code (Claude Code), codex (Codex), cursor (Cursor), other (another agent), none (no agent, written by hand)",
+  "enum": [
+    "claude-code",
+    "codex",
+    "cursor",
+    "other",
+    "none"
+  ],
+  "type": "string"
+}

addedInput schema / properties / model

Added value: +{
+  "description": "The model family behind that agent: claude (Claude), gpt (GPT), gemini (Gemini), other (another model)",
+  "enum": [
+    "claude",
+    "gpt",
+    "gemini",
+    "other"
+  ],
+  "type": "string"
+}

First observedSep 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false, and openWorldHint=false, so the bar is lower. The description adds meaningful context beyond them: the created entity starts as a draft, its id is the key other tools consume, and titles are non-unique so retries can duplicate — directly relevant to the non-idempotent, destructive profile.

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?

Three tight sentences, front-loaded with the core action and the return-value contract. The retry caveat is useful but slightly secondary; still, no sentence is wasted.

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?

Covers the action, the draft state, the id contract for downstream tools, and the duplicate-title hazard. With no output schema, one might want a word on what 'draft' means for later publish steps, but for a 4-param, 2-required tool the essentials are present.

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%, with rich enum descriptions for agent, model, and engine already in the schema. The description adds no parameter-level detail (e.g., which fields are required, engine/title constraints) beyond what the schema documents, so baseline 3 is appropriate.

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+resource ('Create a draft game') and immediately clarifies the return value ('Answers its `id`, which the other tools take'), distinguishing it from sibling read/update tools like get_application and update_application_form. The draft-vs-published distinction adds useful scope.

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?

Gives explicit caveat about non-unique titles and tells the agent to check list_applications before retrying after ambiguous failures, which is genuine when-to-use guidance. It does not name an alternative tool for the create path (there is none), so it stops short of the fullest 'use X instead' phrasing.

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

All Playgama MCP - Publish & Manage HTML5 Games 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.

Resources

Need Help?