Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.facial_analyze_asymmetry

Idempotent

Analyze facial asymmetry as an evidence-based plan before applying changes, mapping semantics to candidates through NLA tracks while preserving the immutable facial plan and body Action.

Instructions

facial_analyze_asymmetry: 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_asymmetry"
  }
}

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?

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotent=true), it adds real behavioral context: candidates are new Actions evaluated through NLA tracks, the body Action is never modified, and 'facial' is an immutable plan.json reference. It also discloses an error condition (TIMING_INPUT_REQUIRED) — though that speech/viseme rule looks irrelevant to an asymmetry analyzer, which is mildly confusing.

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?

Dense, semicolon-chained single block. The leading name restatement is wasted space, and the trailing sentence about speech phonemes/visemes and 'technical QA and artistic review stay separate' reads as boilerplate unrelated to asymmetry analysis, diluting the two actually useful clauses.

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 need no explanation, and the non-destructive plan/apply model plus one error condition are covered. But for a 6-parameter mutation-capable tool with zero schema descriptions, the description leaves the core operation and four parameters unexplained — an agent still cannot reasonably predict what it will get back from a plan run.

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 coverage is 0% across 6 parameters, so the description must carry the burden, and it only partially does. It explains 'apply' (default false, plan first) and 'facial' (immutable plan.json reference), but leaves 'brief', 'intent', 'options', and 'object_name' entirely undefined in both schema and prose — over half the surface area.

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 opens by restating the tool name and then labels it 'M7 facial unit' — internal jargon that tells an agent nothing about what asymmetry analysis actually does. It never states the verb+resource (e.g. 'measures left/right asymmetry of facial shape keys or rig controls') or what constitutes an asymmetry finding. The remaining text is workflow boilerplate that could be pasted onto any of the ~20 facial siblings.

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?

It does convey actionable process guidance: 'plan first, apply=false by default', which tells the agent this is a dry-run unless told otherwise. However there is no differentiation from the many near-identical facial siblings (facial_analyze_bones, facial_analyze_eyes, facial_analyze_jaw, facial_analyze_shape_keys), so an agent cannot tell when this asymmetry analyzer is the right choice versus those.

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