Skip to main content
Glama

export_wav

Render the open VOCALOID6 project’s main mix to a WAV file, or export selected tracks as stems while temporarily muting the others.

Instructions

Render the main mix of the open project to a WAV file (Audio Mixdown). Can take a while. tracks=[...] renders only those tracks (a stem): the others are muted for the export, then mute/solo are restored. / 開いているプロジェクトのメインミックスを WAV に書き出します(時間がかかることがあります)。tracks=[...] で そのトラックだけを書き出します(ステム)。他のトラックは書き出しの間だけミュートし、後で元に戻します。

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": {
      "output": "<output>"
    },
    "name": "export_wav"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputYes
tracksNo
bypass_effectsNo
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description still carries useful behavioral facts: the operation can take a while, and mute/solo state is restored after a stem export. It says nothing about where the file is written, overwrite behavior, blocking/timeout semantics, or whether effects rendering changes the project.

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?

The content is front-loaded: purpose first, then the stem behavior and its cleanup side effect. The Japanese text is a full duplicate of the English, doubling length without adding information, though that is a reasonable localization pattern.

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

Completeness2/5

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

For a four-parameter file-producing tool with no annotations and no output schema, the description leaves key gaps: the meaning and expected form of the required output argument, the effect of bypass_effects, and timeout behavior. Only the tracks parameter and rough runtime are covered.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description must compensate. It only explains tracks and hints at duration ('can take a while'); output (path? filename? directory?), bypass_effects, and timeout_seconds are left entirely undocumented.

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: render the project's main mix to a WAV file (Audio Mixdown), and clarifies the stem variant via tracks=[...]. That is enough to distinguish it from export_midi/export_vsqx by output format, though no sibling is named explicitly.

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?

It gives a concrete rule for the tracks parameter (only those tracks are rendered, others temporarily muted), which implies when to use stem mode versus a full mix. It never states when to prefer this over other export tools or what prerequisites (open project) must hold beyond the passing mention of 'the open project'.

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