Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.animation_generate_locomotion

Generates a locomotion animation plan for a compatible body rig, applying it only when requested and requiring explicit action mapping; source Actions are retained for QA.

Instructions

animation_generate_locomotion: high-level M6 unit. Plan first, apply=false by default; generation is the immutable plan.json reference. Explicit mapping and compatible body rig required. Source Actions retained; technical QA and temporal artistic review are distinct. options carries declared stage parameters, thresholds or visual review; unsupported adapters return concrete errors.

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.animation_generate_locomotion"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo
briefNo
intentNo
optionsNo
generationNo
object_nameNo
operation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3/5.0
Behavior4/5

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

Adds real context beyond the weak annotations: apply defaults to false (dry-run), source Actions are retained rather than overwritten, the generation is an immutable plan.json reference, and unsupported adapters return concrete errors. These are substantive safety and failure-mode disclosures. It still does not describe what apply=true actually mutates or how QA/review gates block progress.

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

Conciseness2/5

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

A single dense run-on sentence of semicolon-separated fragments, front-loaded with a wasted name restatement and the undefined token 'M6'. Useful facts (dry-run default, rig prerequisite, retained sources) are buried rather than structured, so the reader must parse jargon to extract them.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema relieves it of explaining return values, and it does cover workflow order, prerequisites and error behavior. But for a 7-parameter generation tool in a dense sibling family, missing pieces include what locomotion content is produced, the meaning of the brief/intent inputs, and gate conditions for acceptance.

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 carries the full burden. It clarifies apply, generation (immutable plan.json reference) and options (declared stage parameters, thresholds, visual review), but brief, intent, object_name and operation_id are never explained anywhere. Four of seven parameters remain opaque, which is a real gap at this coverage level.

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

Purpose3/5

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

The name carries the actual meaning (generate locomotion animation); the description opens by repeating it and adds only opaque framing like 'high-level M6 unit'. It never states plainly what artifact is produced (a locomotion action/generation) or how it differs from siblings such as animation_generate_idle or animation_generate. Prerequisites ('explicit mapping and compatible body rig') hint at scope but do not define the operation.

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?

'Plan first, apply=false by default' implies a plan-then-apply workflow and correctly signals a dry-run default, which is genuine usage guidance. However, it never names the planning sibling (animation_generation_plan / animation_generation_compatibility) or when to move to apply=true, leaving the agent to infer the sequence. No when-not-to-use guidance is given versus the many other animation_generate_* tools.

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