Unified Scratch MCP: headless TurboWarp VM + block surgery + blocks-to-Python, 117 tools over stdio.
26 tools with inconsistent quality. Most have basic descriptions (50-150 chars) but lack parameter-level detail. Input schemas visible for all tools but many parameters missing descriptions or type constraints. No output schemas documented. Error handling minimal, tools return raw strings without structured guidance. Naming is verb-noun consistent (spy_*, sb3_*, open_*, save_*) but some tools combine multiple concerns (spy_write_python handles both transpilation and file management). No tool annotations (readOnlyHint, destructiveHint). Risk labels present in metadata but not exposed to LLM.
Load an .sb3 file from disk into memory for editing.
Summarize the open project: targets, extensions, monitors and meta.
Write the open project back to an .sb3 file (defaults to the path it was opened from). If the TurboWarp Desktop userscript is installed, the editor reloads the file automatically.
Read current cloud variable values for a project.
Recent cloud activity log for a project.
Set a cloud variable value.
List a user's favorited projects (id + title).
No output schemas documented. Tools return unstructured strings; LLMs cannot plan downstream calls or extract structured data. E.g., spy_project_overview returns a summary string, but no schema defines what fields are present.
Parameter descriptions missing or minimal. 'file' param in spy_read_blocks says 'Tab name (optional)' but does not explain what happens if omitted, what format is expected, or how it relates to spy_open_project. LLMs cannot infer dependencies.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Risk labels exist in metadata (READ_ONLY, WRITE, DESTRUCTIVE) but are not exposed via MCP tool annotations. LLMs cannot see which tools are safe to retry or have side effects.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | <=2025-11-25 | v2 |
Summarise an unpacked project dir: targets, block counts, assets.
Pack a diffable directory back into an .sb3.
Unpack an .sb3 into a diffable directory (project.json + assets/).
List remix lineage info for a project (id, title, author).
Fetch a Scratch studio's title, description, and stats.
Make blocks for an already-installed module (stdlib modules work too).
Remove a tab from the project.
Turn an existing .py file on disk into blocks.
pip install a package and turn it into blocks.
Every kind of block ScratchPy knows, with the Python each one produces.
Python packages installed in the environment ScratchPy uses.
Open (or create) a ScratchPy .spy project file; all other spy_* tools act on it.
What is in the .spy project: tabs, variables, lists, custom blocks, package packs.
Readable outline of every script in a tab.
The Python a tab's blocks generate.
Take a package's blocks back out of the project.
Run a tab's generated Python and return what it printed.
Create a variable or list, or change its starting value.
THE MAIN BUILD TOOL: give ordinary Python, it becomes Scratch blocks in a tab.
Error handling returns raw strings without recovery guidance. spy_run with timeout returns a string; no indication whether to retry, adjust timeout, or ask user. No error classification (retryable vs fatal).
spy_write_python combines transpilation + file management + tab replacement. Should split into separate tools (transpile_python, create_tab, replace_tab) so agent can compose them independently.