Skip to main content
Glama
wfbcargo

spawn-mcp

by wfbcargo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

spawn_getting_started

Start a game project by retrieving the complete workflow: setup order, required art skills, push-screenshot-fix loop, and multi-agent rules; also reports existing project files to show your next step.

Instructions

START HERE before any other spawn tool. The whole workflow in one call: setup order, the art/UI skills to load BEFORE building anything visual, the push → screenshot → fix loop, and the multi-agent rules. Also reports what this project already has (token, variant, game.json, docs) so you know which step you're on. Needs no credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectDirNoAbsolute path to the Spawn game project (game.json / .env). Defaults to SPAWN_PROJECT_DIR or the MCP process cwd.
engineVersionNoOptional engine version this call assumes: a semver ('6.0.0', '5.4') or an era name ('6.0' for a git world, 'document' for a pre-6.0 one). Omit it and the world's engine is detected from the API and cached. When passed it is CHECKED against the real pin and a mismatch fails the call without writing anything — it is an assertion, not an override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • addedInput schema / properties / engineVersion
      Added value: +{
+  "description": "Optional engine version this call assumes: a semver ('6.0.0', '5.4') or an era name ('6.0' for a git world, 'document' for a pre-6.0 one). Omit it and the world's engine is detected from the API and cached. When passed it is CHECKED against the real pin and a mismatch fails the call without writing anything — it is an assertion, not an override.",
+  "type": "string"
+}
  2. Addedv1.4.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations the description carries the full burden, and it does disclose one genuinely useful trait: 'Needs no credentials.' It implies a read/orientation call that inspects the project, but never explicitly states it performs no writes, so the safety profile is inferred rather than declared.

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?

Front-loaded with the imperative 'START HERE,' then a compact enumeration of what the call covers and what it reports. Dense but each clause carries real information; only mild redundancy between 'the whole workflow in one call' and the list that follows.

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?

With no annotations and no output schema, the description must stand alone, and it does describe both the returned workflow content and the project-state summary, which is what an agent needs to orient. It could be slightly more explicit about the return shape, but nothing essential for correct invocation is missing.

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%, so the schema already documents both parameters thoroughly, including engineVersion's assertion-not-override behavior. The description's mention of what it reports (token, variant, game.json, docs) loosely maps to projectDir but adds no semantics the schema lacks; 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?

It names a specific resource (the whole Spawn workflow) and states exactly what the call returns: setup order, skills to load, the push→screenshot→fix loop, multi-agent rules, plus the project's current state. The opening 'START HERE before any other spawn tool' explicitly separates it from siblings like spawn_docs, spawn_status and spawn_me.

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?

The when-to-use is unambiguous: call this first, before any other spawn tool, and it tells you which step you're on from the reported project state. It stops short of naming when a sibling is the better choice once onboarding is done (e.g. spawn_docs for reference), but the routing intent is clear.

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

Deploy Server

Other Tools