Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_vse_text_style

Configure or inspect typography, layout, shadow, outline, and box styling on existing VSE text or subtitle strips to control caption appearance.

Instructions

Configure or inspect typography, layout, shadow, outline, or box styling on an existing text or subtitle strip 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": {
      "name": "<name>"
    },
    "name": "configure_vse_text_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the target text strip.
textNoNew text content to display.
colorNoText color as RGBA [r, g, b, a].
actionNoAction: UPDATE styling properties or INSPECT current configuration.UPDATE
task_idNo
use_boxNoEnable background box behind text.
anchor_xNoHorizontal anchor alignment.
anchor_yNoVertical anchor alignment.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
locationNoNormalized screen coordinates [x, y] (0.0 to 1.0).
use_boldNoRender text in bold weight.
box_colorNoBackground box RGBA color [r, g, b, a].
font_sizeNoFont size in points.
box_marginNoBackground box padding margin.
request_idNo
use_italicNoRender text in italic slant.
use_shadowNoEnable drop shadow behind text.
wrap_widthNoWord wrap width (0.0 = no wrap).
alignment_xNoHorizontal text alignment.
shadow_blurNoShadow edge blur radius.
use_outlineNoEnable text outline stroke.
shadow_colorNoShadow RGBA color [r, g, b, a].
box_roundnessNoBackground box corner roundness (0.0 to 1.0).
outline_colorNoOutline stroke RGBA color [r, g, b, a].
outline_widthNoOutline stroke width.
approval_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only says the tool configures or inspects. It does not disclose that the default action is a mutation, whether omitted styling parameters are left untouched or reset to defaults, whether changes are reversible/undoable, or how the untrusted 'approved'/'approval_token' arguments relate to consent requirements. For a 26-parameter write-capable tool this is a substantial gap.

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 with no filler, and the styling domains are listed compactly. It is efficient, though the flat noun list could have been structured to map onto the action modes or parameter groups more usefully.

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?

With 26 parameters, no annotations, and no output schema, the description should explain the UPDATE versus INSPECT split, what INSPECT returns, and the trust model around the approval fields. None of that is present, so an agent must open the schema and guess at mutation side effects and result shape.

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 88%, so the schema already documents nearly every parameter with types, ranges, and enums. The description adds only a high-level grouping of the domains (typography, layout, shadow, outline, box), which helps orientation but supplies no syntax or semantics beyond the schema. Baseline 3 is appropriate.

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 pair ('Configure or inspect') and a concrete resource ('text or subtitle strip in the VSE') plus the styling domains covered (typography, layout, shadow, outline, box). The word 'existing' implicitly separates it from create_vse_text_strip, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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: the agent can infer this is for styling an already-created strip rather than creating, moving, or trimming one. There is no explicit when-to-use/when-not guidance, no mention that INSPECT is the read path versus UPDATE the write path, and no pointer to alternatives such as modify_vse_strip or transform_vse_strip.

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