Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.facial_generate_saccades

Generate eye saccade animation for Blender facial rigs using evidence-based semantic mapping. Plans candidates as NLA Actions by default without altering the body Action.

Instructions

facial_generate_saccades: M7 facial unit. Evidence-based semantic mapping (never names only); plan first, apply=false by default; facial is the immutable plan.json reference. Candidates are new Actions evaluated through NLA tracks; the body Action is never modified. Speech needs explicit timed phonemes/visemes (TIMING_INPUT_REQUIRED otherwise). Technical QA and artistic review stay separate.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "production.facial_generate_saccades"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo
briefNo
facialNo
intentNo
optionsNo
object_nameNo
operation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.5/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations: it discloses that facial is an immutable plan.json reference, that the body Action is never modified, and that output candidates are new Actions evaluated through NLA tracks, plus a TIMING_INPUT_REQUIRED failure condition. It stops short of stating permissions or exactly what the candidate contains, but the core mutation footprint is clear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is compact and front-loads the plan-first/apply-default behavior, but the sentences are telegraphic semicolon chains with unexplained taxonomy ("M7") and a trailing "Technical QA and artistic review stay separate" that reads as boilerplate rather than actionable content.

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 7-parameter generator with 0% schema description coverage, the description omits the meaning of most parameters and the speech timing input contract is only alluded to. The output schema covers return values, but the input-side gaps keep this from being complete enough to invoke confidently.

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 7 parameters, so the description must carry the whole load. It only clarifies two of them (apply defaults to false, facial is the immutable plan.json reference) and leaves brief, intent, options, object_name, and operation_id completely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"M7 facial unit" plus the restated name is jargon, not a description of what the tool does. It never says these are saccade eye movements or how they differ from siblings like facial_generate_gaze, facial_coordinate_gaze, or facial_plan_blinks, so an agent cannot distinguish the tool from its neighbors on purpose alone.

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?

"plan first, apply=false by default" implies a plan-then-apply workflow, which is useful, but there is no explicit when-to-use/when-not guidance relative to the many adjacent gaze/blink/lipsync tools. The speech prerequisite clause is conditional context, not routing guidance for selecting this tool.

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