---
name: sound-vocab-jobs
description: "Step-by-step job recipes for the Sound Vocabulary MCP server: Make a sound effect from a description; List the sound vocabulary by UCS category. Use when the user asks things like \"I need a short soft click sound for a toggle switch in my app.\" or \"What cartoon sound effects do you have?\""
license: MIT
---

# Sound Vocabulary jobs

Each section below walks through one job with the tools of the `sound-vocab` MCP server. The same recipes are MCP prompts (prompts/list) on `https://soundvocab.openkrill.app/mcp`.
Connect the server at `https://soundvocab.openkrill.app/mcp` in your MCP client settings (remote streamable HTTP, no key), then call its tools as normal tool calls. They are not command line programs: Bash, curl and scripts cannot reach them.

## Make a sound effect from a description

Job: Make a sound effect from a description, with the Sound Vocabulary MCP server.

Use the `make_sound` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "I need a short soft click sound for a toggle switch in my app."

Steps:
1. Call `make_sound` as a normal MCP tool call, with the request's values in the fields of its inputSchema.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"describe":"a short soft click for a toggle"}`
4. For the request "I need a short soft click sound for a toggle switch in my app.", a correct answer looks like this: A UI click or toggle sound with a WAV link and a Web Audio play function.
5. Follow the server's own rules:
   - Use make_sound with the person's words as describe; pass pitch, length or brightness only when they give a number.
   - Show the sound name, its UCS category, the wav_url and page_url, and put code in a code block, exactly as returned, when they build an app or a game; never write your own synthesis code instead.
   - Offer the alternatives when the match may not fit.
   - Never claim a sound is a recording; each is a synthesis recipe under CC0.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `make_sound`).

## List the sound vocabulary by UCS category

Job: List the sound vocabulary by UCS category, with the Sound Vocabulary MCP server.

Use the `list_sounds` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "What cartoon sound effects do you have?"

Steps:
1. Call `list_sounds` as a normal MCP tool call, with the request's values in the fields of its inputSchema.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"category":"CARTOON"}`
4. For the request "What cartoon sound effects do you have?", a correct answer looks like this: Cartoon sounds such as the zip, the boing and the bonk, with WAV links.
5. Follow the server's own rules:
   - Show the sound name, its UCS category, the wav_url and page_url, and put code in a code block, exactly as returned, when they build an app or a game; never write your own synthesis code instead.
   - Offer the alternatives when the match may not fit.
   - Use list_sounds to browse.
   - Never claim a sound is a recording; each is a synthesis recipe under CC0.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `list_sounds`).