Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.facial_analyze_hybrid

Idempotent

Analyze facial animation evidence to plan semantic mappings and optionally apply candidates as new NLA Actions while preserving the body and immutable facial reference.

Instructions

facial_analyze_hybrid: 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_analyze_hybrid"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo
briefNo
facialNo
intentNo
optionsNo
object_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.8/5.0
Behavior4/5

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

Adds meaningful context beyond annotations: 'the body Action is never modified,' candidates become 'new Actions evaluated through NLA tracks,' and 'facial is the immutable plan.json reference,' which reassures despite readOnlyHint=false. It also discloses a failure mode ('TIMING_INPUT_REQUIRED otherwise'), useful given the mutation-flavored flags.

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?

The preamble names the tool redundantly, and phrases like 'never names only' waste space, while dense jargon crowds out the core purpose. It is compact but poorly front-loaded toward what the tool does.

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?

An output schema exists so return values needn't be described, and behavioral constraints are covered well. But with six undocumented params, no sibling differentiation, and an opaque core purpose, the description is not complete enough for correct invocation.

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% for six parameters, to compensate for which the description only clarifies 'facial' (plan.json reference) and the 'apply' default, while brief, intent, options, and object_name remain unexplained. Half or more of the parameters get no added meaning.

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?

The description leads with internal jargon ('M7 facial unit', 'Evidence-based semantic mapping') and never states a concrete verb+resource for what actually gets analyzed. It gives no differentiation from the many sibling analyzers (facial_analyze_lips, facial_analyze_bones, etc.), leaving the agent unable to tell this apart from other facial analysis tools.

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' and keeping 'Technical QA and artistic review separate' imply a workflow context. However, there is no explicit when-to-use vs. when-not, and no routing to any of the large set of facial siblings.

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