Skip to main content
Glama
Sign In
scratch-unified-mcp

scratch-unified-mcp

by blessed0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Project Add Sound

project_add_sound

Adds an MP3 or WAV sound file to a sprite in a Scratch project, copying it into the project's assets. Accepts only these formats to prevent project load errors.

Instructions

Add a sound to a sprite, copying the file into the project's assets/.

Scratch accepts only MP3 and WAV; other formats make the project refuse to load, with no warning.

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": {
      "sprite": "<sprite>",
      "file": "<file>"
    },
    "name": "project_add_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesPath to an .mp3 or .wav file.
nameNoSound name in Scratch. Defaults to the filename without its extension.
pathNoProject to modify. Defaults to the active project.
spriteYesSprite name, i.e. its .gs filename without the extension. The Stage is "stage".

Output Schema

NameRequiredDescriptionDefault
kindYes
nameYes
pathYes
existsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does meaningful work: it discloses the file-copy side effect into assets/ and warns about the silent failure mode where unsupported formats make the project refuse to load with no warning. This is high-value behavioral disclosure, though it omits details like name-conflict behavior, permissions, or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no filler: the core action and side effect are front-loaded, followed immediately by the critical format warning. Every word earns its place.

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?

For a mutation tool with no annotations, the description covers the essential ground: purpose, side effect, and the most damaging failure mode. The 100%-coverage schema and existing output schema fill in parameter and return semantics. Minor gaps remain around conflict handling and reversibility, but nothing critical 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 coverage is 100%, so the schema already documents all four parameters (file, name, path, sprite) with descriptions. The description reinforces the format restriction for file but adds little semantic value beyond what the schema provides; the baseline of 3 applies.

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 — 'Add a sound to a sprite, copying the file into the project's assets/' — which clearly identifies the tool's function and distinguishes it from removal tools like project_remove_asset and costume tools like project_add_costume. It does not explicitly differentiate from the similar sb3_add_sound sibling, so it falls just short of full clarity.

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

Usage Guidelines3/5

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

The description provides practical usage guidance via the format constraint ('Scratch accepts only MP3 and WAV') and implies the intended context of working with project sprites. However, it gives no explicit when-to-use vs. when-not-to-use guidance or alternative routing against siblings such as sb3_add_sound or project_add_costume, leaving selection to inference.

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