Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

manage_vse_sound_modifiers

Add, remove, update, or list audio modifiers such as equalizer, pitch, and echo on VSE sequencer strips to control strip sound.

Instructions

Add, remove, update, or list audio modifiers (SOUND_EQUALIZER, PITCH, ECHO) on sequencer strips (MetaStrips, MovieStrips, or Adjustment strips) in the 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": {
      "action": "<action>",
      "name": "<name>"
    },
    "name": "manage_vse_sound_modifiers"
  }
}

Input Schema

NameRequiredDescriptionDefault
mixNoEcho dry/wet mix factor (0.0 to 1.0).
muteNoMute modifier effect.
nameYesTarget strip name.
centsNoFine cents shift for PITCH modifier (-100 to +100).
delayNoEcho delay in seconds for ECHO modifier.
ratioNoFrequency ratio multiplier for PITCH modifier.
actionYesAction to perform on strip sound modifiers.
enableNoEnable or disable modifier in viewport/rendering.
qualityNoPitch algorithm quality (1 to 5).
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
feedbackNoEcho feedback repetition amount (0.0 to 1.0).
semitonesNoSemitone shift for PITCH modifier (-36 to +36).
pitch_modeNoPitch adjustment method for PITCH modifier.
request_idNo
modifier_nameNoName of modifier (optional for ADD/LIST, required for REMOVE/UPDATE).
modifier_typeNoModifier type (required for ADD).
approval_tokenNo
preserve_formantNoPreserve vocal formants when shifting pitch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it only discloses the supported strip types. It says nothing about whether mutations are undoable, what permissions/context are required, which parameters become mandatory per action or per modifier type, or what LIST returns. For a 19-parameter mutation tool with zero annotation coverage, these are material omissions.

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?

A single front-loaded sentence with the verb list first, then resource, then enumerated subtypes in parentheses. No filler, and every clause carries information.

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?

The description covers purpose, resource scope, and valid types for a complex 19-parameter tool; the remaining gaps (per-action required parameters, permissions, return shape) are partly absorbed by a rich, 84%-documented schema with enums constraining action, modifier_type, and pitch_mode. It is adequate, though stronger behavioral disclosure would be needed absent annotations.

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 84%, so the schema already explains most parameters (echo mix/feedback/delay, pitch semitones/cents/ratio/quality/formant, modifier_name/modifier_type requirements). The description adds only the supported strip-type enumeration, which maps loosely to the 'name' parameter. Baseline 3 is appropriate given the schema does the heavy lifting.

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 names specific verbs (add, remove, update, list) and a concrete resource (audio modifiers), plus enumerates the modifier types and supported strip types, so the agent knows exactly what domain it operates in. It stops short of distinguishing itself from the near-identically named sibling manage_vse_strip_modifiers, which is the main thing an agent would need to disambiguate.

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?

The four action values imply when each mode applies, but there is no explicit guidance on when to pick this tool over manage_vse_strip_modifiers or inspect_modifiers, nor any stated preconditions (e.g. strip must exist, must be one of the three listed types). Usage is inferable rather than stated.

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