Sceneplane

Generate 16-bit game audio

audio_generate

Idempotent

Synthesize deterministic 16-bit PCM WAV game audio as a job artifact: sfx presets (jump, coin, laser, explosion, powerup, hit, blip, pickup), win/lose jingles, or loopable BGM (exact-bar loops from bpm, bars, root, scaleMode, voice). Same payload + seed always returns identical bytes. The WAV arrives as an audio_wav artifact with a download URL in job_get.

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": {
      "projectId": "<projectId>",
      "audioKind": "<audioKind>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "audio_generate"
  }
}

Input Schema

Name	Required	Description	Default
`bpm`	No
`bars`	No	bgm loop length, 4/4 bars
`root`	No		C
`seed`	No
`pitch`	No	sfx frequency multiplier
`voice`	No		square
`preset`	No	sfx: jump\|coin\|laser\|explosion\|powerup\|hit\|blip\|pickup; jingle: win\|lose
`audioKind`	Yes
`projectId`	Yes	Stable project ID returned by project_create or projects_list.
`scaleMode`	No		major
`idempotencyKey`	Yes	Stable caller-chosen key for safe retries of this same request.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true and readOnlyHint=false, and the description reinforces this with the determinism guarantee ('same payload + seed always returns identical bytes'), which is real added context. It also discloses the asynchronous job-artifact flow and where the result lands (audio_wav artifact, URL via job_get). It does not mention generation latency, cost, or failure modes for invalid preset/kind combinations.

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?

Two tight sentences, front-loaded with the output format and the determinism contract, followed by the mode enumeration and result location. No filler or repetition of the title.

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 an async mutation tool with no output schema, the description covers the return path (artifact plus download URL retrievable through job_get) and the determinism guarantee. Minor gaps remain around per-mode parameter requirements and what a job submission returns immediately, but the essential calling information is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 45% schema coverage across 11 parameters, the description usefully maps parameters to modes (bpm/bars/root/scaleMode/voice apply to bgm; preset to sfx and jingle), a conditional applicability the schema does not express. It leaves pitch, seed semantics per mode, and projectId/idempotencyKey behavior unexplained beyond the schema's own text.

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?

States a specific verb and resource ('Synthesize deterministic 16-bit PCM WAV game audio as a job artifact') and enumerates the three supported modes (sfx presets, win/lose jingles, loopable BGM). An agent can distinguish this from audio_inspect or asset_generate_3d without opening the schema.

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?

Usage context is clear: pick sfx for one-shot effects, jingle for win/lose stingers, bgm for exact-bar loops, and it notes the payload+seed combination is what guarantees identical output. It does not name an alternative tool or state when not to use this one, so it stops short of explicit routing guidance.

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

All Sceneplane tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?