Title100/100
Plan Wavedash Implementation
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Plan and guide a Wavedash browser game integration from the user's goal, engine, and requested features. Call this first for any request to build, deploy, upload, or release a game on Wavedash, or to add Wavedash SDK features. Choose the stage: plan (architecture and reading order), setup (CLI install, sign-in, SDK init, wavedash.toml, local testing), features (SDK reference for the requested features), or deploy (upload and release checklist). Returns ordered steps, boundaries, and the relevant docs.wavedash.com pages with content. Read-only and unauthenticated.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
goal
What the user wants to build, deploy, or integrate, including the game type and the Wavedash outcome.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
engine
Optional engine or framework as the user names it, for example Phaser, Unity WebGL, Godot 4, three.js, React, Rust, or custom.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
features
Optional requested Wavedash features, for example multiplayer, leaderboards, achievements, cloud saves, ugc, players, paid content.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
stage
plan: architecture and reading order. setup: CLI, SDK init, config, local testing. features: SDK reference for the requested features. deploy: upload and release checklist.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
{
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}Output schema92/100
The output schema explains the structured result.
View output schema
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"text",
"stage",
"goal",
"engine",
"features",
"steps",
"docs",
"boundaries",
"next_tools"
],
"properties": {
"docs": {
"type": "array",
"items": {
"type": "object",
"required": [
"slug",
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Full docs.wavedash.com URL."
},
"slug": {
"type": "string",
"description": "Docs path, for example sdk/setup."
}
},
"additionalProperties": false
},
"description": "Docs pages to read for this stage."
},
"goal": {
"type": "string"
},
"text": {
"type": "string",
"description": "Human-readable plan."
},
"stage": {
"enum": [
"plan",
"setup",
"features",
"deploy"
],
"type": "string"
},
"steps": {
"type": "array",
"items": {
"type": "string"
},
"description": "Ordered implementation steps for this stage."
},
"engine": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
]
},
"features": {
"type": "array",
"items": {
"type": "string"
}
},
"boundaries": {
"type": "array",
"items": {
"type": "string"
},
"description": "What this MCP and Wavedash do not do."
},
"next_tools": {
"type": "array",
"items": {
"type": "string"
},
"description": "Recommended follow-up tool calls."
}
},
"additionalProperties": false
}