Rengi Forge

audio_tools_variations

Make 2-12 variations of one sound effect with small pitch and volume changes, so repeated footsteps or hits do not sound copy-pasted. Returns each file and a ZIP. Price: $0.10 USDC via x402, charged only on success. Part of Audio tools: Make generated or recorded sounds game-ready: trim silence and match loudness (LUFS with a true-peak ceiling), seamless loops for music and ambience with loop points, and SFX variations.

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": "audio_tools_variations"
  }
}

Input Schema

Name	Required	Description	Default
`mono`	No
`seed`	No
`audio`	No	Audio file as base64 (wav, mp3, ogg, flac, m4a).
`count`	No
`format`	No		ogg
`audioUrl`	No	Audio file URL.
`volumeDb`	No	Max volume change either way.
`pitchSemitones`	No	Max pitch change either way.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 20, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the return format (each file plus a ZIP) and the billing model ($0.10 USDC via x402, charged only on success), but says nothing about determinism of the seed, input size limits, or processing failure modes.

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?

Front-loads the core action and effect in the first sentence, then stacks return format and pricing efficiently. The trailing 'Part of Audio tools' sentence is somewhat boilerplate but earns its place by disambiguating family siblings.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter tool with no output schema and no annotations, the description covers purpose, return format, and cost adequately but omits explanation of several parameters (mono, seed, format) and any input-format constraint. It is workable but leaves gaps the structured fields do not fill.

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 description coverage is 50%, so the description must compensate. It does add meaning for count ('2-12 variations') and pitch/volume ('small pitch and volume changes'), but leaves mono, seed, and format completely unexplained in both schema and description.

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 ('Make 2-12 variations of one sound effect') with the operative mechanism (small pitch and volume changes). The closing family sentence distinguishes it from siblings audio_tools_clean (trim/loudness) and audio_tools_loop (loops), so an agent can route correctly without opening schemas.

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?

Gives a clear use scenario ('so repeated footsteps or hits do not sound copy-pasted') that tells the agent when this tool is appropriate. It does not explicitly state when NOT to use it or name a preferred alternative, so it stops short of a 5.

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

All Rengi Forge tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?