scratch-unified-mcp

Overview Schema Source Related Servers Discussions Admin

Sb3 Reload

sb3_reload

Reload a local .sb3 file into TurboWarp Desktop to update the running Scratch project, enabling iterative testing after file changes.

Instructions

Load an .sb3 from disk in TurboWarp Desktop via bridge. (proxied)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sb3_reload"
  }
}

Input Schema

Name	Required	Description	Default
`path`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 19, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description must carry the behavioral disclosure burden. It reveals that the operation is a load through a bridge and is proxieed, but it does not state whether the current project is replaced, whether TurboWarp Desktop must be running, or what side effects or errors may occur.

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 a single, front-loaded sentence with no filler. The '(proxied)' suffix is concise though somewhat cryptic.

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?

Despite a simple one-param signature, the description is too thin to fully guide invocation: it lacks path semantics, side effects, and interaction with the current project. Overlapping sibling tools increase the need for a richer description.

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?

The schema has one 'path' paramater with 0% description coverage. The description's 'from disk' clarifies that path refers to a local .sb3 file, but it does not explain path format, the default empty string, or whether extensions are required.

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 action ('Load an .sb3 from disk') and a specific environment ('TurboWarp Desktop via bridge'), making the tool's core purpose clear. It does not explicitly contrast with siblings like sb3_open_project or project_open, so it falls short of full differentiation.

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?

No guidance is given about when to use this tool versus the many overlapping project-opening siblings. The parenthetical '(proxied)' hints at a special context but does not explain a decision rule for choosing this tool.

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

Deploy Server