save_experience_game_proposal
FIRST step for creating or revising a game. Save a proposal document and a visible Games tab entry, then STOP for human approval. Markdown must have headings starting Concept, Gameplay, Controls, Screens, Files, and Playtest. Describe audience, objective/core loop/levels/win/loss, desktop/touch controls, visual/audio direction, start/pause/help/score/game-over/restart UI, code organization and assets, and concrete checks. Do not include game code. For an existing game read it first and pass expectedVersionId and expectedProposalRevision. For a modular Worldstream attachment supply worldExperienceTarget with its liveWorldId, inputBindingId, and current expectedVersionId. An approved build automatically pins the new game version only if that world version is still current. A revised proposal always needs fresh approval.
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": {
"workspaceId": "<workspaceId>",
"title": "<title>",
"description": "<description>",
"proposalMarkdown": "<proposalMarkdown>"
},
"name": "save_experience_game_proposal"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| gameId | No | ||
| prompt | No | ||
| worldId | No | ||
| description | Yes | ||
| workspaceId | Yes | ||
| proposalMarkdown | Yes | ||
| expectedVersionId | No | ||
| worldExperienceTarget | No | ||
| expectedProposalRevision | No |