Simpler.Asia

studio.enhance_audio

Clean up an audio clip on the timeline: noise removal, voice shaping, loudness normalization. FREE (platform compute, no provider). Mints an enhanced asset beside the original - the original is never destroyed.

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": {
      "project_id": "<project_id>",
      "clip_id": "<clip_id>"
    },
    "name": "studio.enhance_audio"
  }
}

Input Schema

Name	Required	Description
`noise`	No	Remove background noise.
`voice`	No	Shape for speech (high-pass, compress, de-ess).
`clip_id`	Yes	Audio clip on the timeline to enhance.
`normalize`	No	Normalize loudness to broadcast level.
`project_id`	Yes	The studio project (vp_…) this tool acts on.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With only readOnlyHint=false in annotations, the description carries real weight and delivers: it is free (platform compute, no provider cost) and non-destructive ('mints an enhanced asset beside the original — the original is never destroyed'). What's missing is timing/async behaviour and whether the enhanced asset lands on the same track or a new one.

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?

Three short sentences, front-loaded with what it does, then cost, then the non-destructive guarantee. Zero filler and no repetition of the schema.

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?

There is no output schema, so the description should say what the caller gets back, yet it only says an asset is 'minted beside the original' without indicating whether an asset id is returned or how to reference it downstream. The safety and cost story is complete; the return contract is not.

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%, with each of noise/voice/normalize already described as booleans with defaults, so the description adds little beyond restating the same three processing names. Per the high-coverage rule the baseline of 3 applies; nothing about defaults or interactions between flags is added.

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?

Specific verb and resource: 'Clean up an audio clip on the timeline' followed by the three concrete operations (noise removal, voice shaping, loudness normalization). This separates it from neighbours like studio.generate_voiceover or studio.remove_silence, though it never names those siblings directly, so the differentiation is by enumeration rather than explicit routing.

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?

Usage is only implied by 'an audio clip on the timeline'. There is no statement of when to reach for this versus studio.adjust_audio_levels, studio.remove_silence, or studio.set_ducking, and no prerequisites (e.g. does the clip need prior transcription?). Implied fit, no exclusions.

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

All Simpler.Asia 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?