Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

transform_vse_strip

Configure or inspect 2D transform properties—offset, scale, rotation, origin, and filter—for a Video Sequence Editor strip by name.

Instructions

Configure 2D transform attributes (offset_x, offset_y, scale_x, scale_y, rotation, origin, filter) on a strip 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": "transform_vse_strip"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the target strip in the sequence editor.
actionNoAction: UPDATE transform properties or INSPECT current transform.UPDATE
filterNoInterpolation filter method.
originNoOrigin pivot point [x, y] in normalized coordinates (0.0 to 1.0).
scale_xNoHorizontal scale factor (1.0 = 100%).
scale_yNoVertical scale factor (1.0 = 100%).
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
offset_xNoHorizontal translation offset in pixels.
offset_yNoVertical translation offset in pixels.
rotationNoRotation angle in radians.
request_idNo
approval_tokenNo

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?

With no annotations at all, the description carries the full behavioral burden and does not meet it. It never states whether unspecified properties are preserved or reset on a partial update, that the tool also has a read-only INSPECT mode despite the 'Configure' framing, or what the approval_token/approved parameters imply for execution. These are material gaps for a mutation tool with zero annotation coverage.

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?

One front-loaded sentence with the verb and resource stated first and no filler. The parenthetical parameter list is somewhat redundant against the schema, which costs a point, but the sentence is otherwise tight and readable.

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 tool with no annotations and no output schema, a single sentence is thin. Missing are partial-update semantics, the dual UPDATE/INSPECT behavior, error conditions when the named strip is absent, and any indication of what the operation returns. The agent is left guessing on several decisions that affect correct invocation.

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 documents most parameters with units and defaults (pixels, normalized 0-1 origin, radians, 1.0 = 100%). The description only re-lists property names already present in the schema and adds nothing about the UPDATE/INSPECT action, task_id, request_id, or approval_token. Baseline 3 applies since 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 uses a specific verb ('Configure') plus the exact resource ('2D transform attributes on a strip in the Video Sequence Editor') and enumerates the affected properties. An agent can immediately tell this mutates transform state rather than strip content. It does not distinguish itself from siblings like transform_object or animate_vse_strip, so it stops short of a 5.

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?

There is no guidance on when to use this tool versus alternatives such as animate_vse_strip (animated transforms) or transform_object, and no prerequisites are stated (e.g., the strip must already exist in the sequence). The schema exposes an UPDATE/INSPECT action, but the description never explains which situation calls for which, leaving the agent to infer selection.

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