Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_vse_audio

Configure volume, pan, pitch correction, waveform display, mute, and fade-in/fade-out on a Video Sequence Editor sound strip.

Instructions

Configure audio properties (volume, pan, pitch correction, waveform display, mute, fade-in/fade-out) on a SoundStrip in the Video Sequence Editor (VSE).

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

Input Schema

NameRequiredDescriptionDefault
panNoStereo panning (-1.0 = full left, 0.0 = center, 1.0 = full right).
muteNoMute audio playback for this strip.
nameYesName of the target audio/sound strip.
actionNoAction: UPDATE audio settings or INSPECT current configuration.UPDATE
volumeNoPlayback volume multiplier (1.0 = 100%, 0.0 = silent).
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
request_idNo
show_waveformNoDraw audio waveform inside the timeline strip.
approval_tokenNo
fade_in_durationNoDuration in frames for linear volume fade-in from strip start.
pitch_correctionNoMaintain audio pitch when strip playback speed is retimed.
fade_out_durationNoDuration in frames for linear volume fade-out to strip end.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It says the tool configures properties but does not disclose mutation semantics, reversibility, approval/auth requirements, the meaning of the INSPECT action, side effects, or return behavior.

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?

A single front-loaded sentence that identifies the resource and lists the main configuration dimensions without wasted words. It is appropriately sized for a preliminary summary, though it could be organized further to separate mutation behavior from inspect behavior.

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 13-parameter mutation tool with no annotations and no output schema, the description is too thin. It omits important context about the UPDATE versus INSPECT actions, approval/token handling, what happens to unspecified properties, and what the caller can expect from a successful call.

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 77%, so the schema already explains most parameters well. The description adds only a general field list and does not clarify the action enum, approval-related fields, or how omitted settings are handled.

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?

States a specific verb and resource: configure audio properties on a SoundStrip in the Video Sequence Editor. The parenthetical field list makes the scope concrete, though it does not distinguish this tool from nearby siblings such as mixdown_vse_audio or manage_vse_sound_modifiers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no explicit guidance on when to use this tool versus alternatives or when not to use it. The only implied usage is that an agent should call it to change audio settings, with no prerequisites, exclusions, or sibling routing.

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

Deploy Server

Other Tools