Spritulus Game Creator

create_game

Destructive

Create a game. Provide a name, description, scene style, and environment ID.

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": {
      "name": "<name>",
      "description": "<description>",
      "sceneStyleKey": "<sceneStyleKey>",
      "environmentId": "<environmentId>"
    },
    "name": "create_game"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`spriteId`	No
`introText`	No
`objective`	No
`tilesetId`	No
`timeLimit`	No
`description`	Yes
`npcDialogue`	No
`tilemapData`	No
`environmentId`	Yes
`healthBarType`	No
`sceneStyleKey`	Yes
`timeBasedScore`	No
`bestTwoOutOfThree`	No
`buttonNineSliceId`	No
`characterDialogue`	No
`objectiveElementType`	No
`additionalElementType`	No
`objectiveElementMovement`	No
`objectiveElementSpriteId`	No
`additionalElementMovement`	No
`additionalElementSpriteId`	No
`objectiveElementAttachmentType`	No
`additionalElementAttachmentType`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=false, but the description adds no behavioral context beyond those flags. It does not explain side effects, prerequisites such as whether the environment must already exist, or what happens when creation succeeds.

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?

The description is two short sentences with no filler and the action is front-loaded. It is efficiently written, though extremely terse for a tool with 24 parameters.

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

Completeness2/5

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

For a complex create tool with 24 parameters, no output schema, and 0% schema description coverage, the description covers only the required fields. It omits optional parameters, return behavior, and creation side effects, so an agent cannot fully understand how to use the tool beyond a minimal call.

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 description coverage is 0% and there are 24 parameters. The description mentions only the four required fields, name, description, scene style, and environment ID, leaving the other 20 optional parameters entirely undocumented in both the schema and the description.

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 states a specific verb and resource: 'Create a game.' This clearly separates it from get_game, update_game, and list_games by name, but it does not distinguish it from nearby create_* siblings such as create_scene or create_template.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, no exclusions, and no alternatives. It only lists four required fields, leaving an agent to infer when create_game should be chosen over update_game or the other create_* tools.

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

All Spritulus Game Creator 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?